CVE-2026-10648

NULL-pointer dereference in MCUmgr serial/console SMP transport on buffer-pool exhaustion

Published Jun 29, 2026 CVSS 3.1 · 6.2 Medium EPSS < 1% KEV · Not listed
Description
mcumgr_serial_process_frag() in subsys/mgmt/mcumgr/transport/src/serial_util.c calls net_buf_reset() on the result of smp_packet_alloc() before checking it for NULL. smp_packet_alloc() uses net_buf_alloc(K_NO_WAIT) against the shared MCUmgr packet pool (CONFIG_MCUMGR_TRANSPORT_NETBUF_COUNT, default 4), which returns NULL when the pool is exhausted. In default builds the __ASSERT_NO_MSG in net_buf_reset is a no-op, so net_buf_simple_reset writes through the NULL pointer (buf->len = 0; buf->data = buf->__buf), causing a fault/crash.

The fragment data reaches this code from attacker-controlled bytes on the MCUmgr serial/UART/shell-console transports (smp_uart.c, smp_raw_uart.c, smp_shell.c), and a fresh buffer is allocated at the start of essentially every new packet. An attacker on the serial/console link can flood the transport to drive the 4-entry buffer pool to exhaustion and induce the NULL dereference, crashing the device (denial of service).

The defect was introduced after the original MCUmgr rework and shipped in Zephyr v4.4.0. The fix moves the NULL check ahead of net_buf_reset.

Analysis

AI-generated

Technical impact

In Zephyr, the function mcumgr_serial_process_frag in serial_util.c performs a net_buf_reset on a buffer returned by smp_packet_alloc before verifying that the allocation succeeded. smp_packet_alloc pulls a buffer from the shared MCUmgr packet pool (CONFIG_MCUMGR_TRANSPORT_NETBUF_COUNT, default 4) using net_buf_alloc(K_NO_WAIT). When the pool is exhausted smp_packet_alloc returns NULL. Because the default build treats the __ASSERT_NO_MSG in net_buf_reset as a no‑op, net_buf_simple_reset writes through the NULL pointer, setting buf->len to 0 and buf->data to buf->__buf, which causes a fault and crashes the device. The buffer is requested at the start of every new packet received over the MCUmgr serial/UART/shell-console transports. An attacker who can send packets over these interfaces can flood the transport, exhaust the four‑entry buffer pool, and trigger the NULL dereference, resulting in a denial‑of‑service crash.

Affected Systems

Zephyr project’s Zephyr RTOS in its default configuration is affected. The vulnerability was introduced after the MCUmgr rework and shipped in Zephyr v4.4.0. Any builds derived from that version that use the default 4‑entry buffer pool are vulnerable. The issue is resolved in newer releases that incorporate the NULL check before resetting the buffer.

Risk and Exploitability

The CVSS score of 6.2 indicates moderate severity. The EPSS score is < 1% and the vulnerability is not listed in CISA KEV. The attack vector is a local serial or console interface, which may be accessible if the device is physically present or if the console is remote. By sending a stream of packets over the MCUmgr serial/UART/shell-console transports, an attacker can exhaust the pool and trigger the crash. No privilege escalation is required and the crash is deterministic, so the risk is significant for devices exposed to the serial console.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the official Zephyr patch that introduces a NULL check before calling net_buf_reset; the relevant commit 6f363ec6f7fd6ae9ed7ca2ae66fd9c82dce31c59 is available in newer Zephyr releases such as 4.4.1 and later.
  • If the application does not need MCUmgr over the serial/console interface, disable or remove the SMP transport modules smp_uart.c, smp_raw_uart.c, and smp_shell.c to eliminate the attack surface.
  • Implement access controls on the serial/console port, such as authentication, physical access restrictions, or secure tunneling, to prevent an attacker from flooding the transport and exhausting the buffer pool.

Generated by OpenCVE AI on July 31, 2026 at 16:40 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description mcumgr_serial_process_frag() in subsys/mgmt/mcumgr/transport/src/serial_util.c calls net_buf_reset() on the result of smp_packet_alloc() before checking it for NULL. smp_packet_alloc() uses net_buf_alloc(K_NO_WAIT) against the shared MCUmgr packet pool (CONFIG_MCUMGR_TRANSPORT_NETBUF_COUNT, default 4), which returns NULL when the pool is exhausted. In default builds the __ASSERT_NO_MSG in net_buf_reset is a no-op, so net_buf_simple_reset writes through the NULL pointer (buf->len = 0; buf->data = buf->__buf), causing a fault/crash. The fragment data reaches this code from attacker-controlled bytes on the MCUmgr serial/UART/shell-console transports (smp_uart.c, smp_raw_uart.c, smp_shell.c), and a fresh buffer is allocated at the start of essentially every new packet. An attacker on the serial/console link can flood the transport to drive the 4-entry buffer pool to exhaustion and induce the NULL dereference, crashing the device (denial of service). The defect was introduced after the original MCUmgr rework and shipped in Zephyr v4.4.0. The fix moves the NULL check ahead of net_buf_reset. mcumgr_serial_process_frag() in subsys/mgmt/mcumgr/transport/src/serial_util.c calls net_buf_reset() on the result of smp_packet_alloc() before checking it for NULL. smp_packet_alloc() uses net_buf_alloc(K_NO_WAIT) against the shared MCUmgr packet pool (CONFIG_MCUMGR_TRANSPORT_NETBUF_COUNT, default 4), which returns NULL when the pool is exhausted. In default builds the __ASSERT_NO_MSG in net_buf_reset is a no-op, so net_buf_simple_reset writes through the NULL pointer (buf->len = 0; buf->data = buf->__buf), causing a fault/crash. The fragment data reaches this code from attacker-controlled bytes on the MCUmgr serial/UART/shell-console transports (smp_uart.c, smp_raw_uart.c, smp_shell.c), and a fresh buffer is allocated at the start of essentially every new packet. An attacker on the serial/console link can flood the transport to drive the 4-entry buffer pool to exhaustion and induce the NULL dereference, crashing the device (denial of service). The defect was introduced after the original MCUmgr rework and shipped in Zephyr v4.4.0. The fix moves the NULL check ahead of net_buf_reset.
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Zephyrproject
Zephyrproject zephyr
Vendors & Products Zephyrproject
Zephyrproject zephyr
Type Values Removed Values Added
Description mcumgr_serial_process_frag() in subsys/mgmt/mcumgr/transport/src/serial_util.c calls net_buf_reset() on the result of smp_packet_alloc() before checking it for NULL. smp_packet_alloc() uses net_buf_alloc(K_NO_WAIT) against the shared MCUmgr packet pool (CONFIG_MCUMGR_TRANSPORT_NETBUF_COUNT, default 4), which returns NULL when the pool is exhausted. In default builds the __ASSERT_NO_MSG in net_buf_reset is a no-op, so net_buf_simple_reset writes through the NULL pointer (buf->len = 0; buf->data = buf->__buf), causing a fault/crash. The fragment data reaches this code from attacker-controlled bytes on the MCUmgr serial/UART/shell-console transports (smp_uart.c, smp_raw_uart.c, smp_shell.c), and a fresh buffer is allocated at the start of essentially every new packet. An attacker on the serial/console link can flood the transport to drive the 4-entry buffer pool to exhaustion and induce the NULL dereference, crashing the device (denial of service). The defect was introduced after the original MCUmgr rework and shipped in Zephyr v4.4.0. The fix moves the NULL check ahead of net_buf_reset.
Title NULL-pointer dereference in MCUmgr serial/console SMP transport on buffer-pool exhaustion
Weaknesses CWE-476
References
Metrics cvssV3_1

{'score': 6.2, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
zephyr
Published
Updated
Nov 4, 2026, 4:58 AM
Reserved
Jun 2, 2026, 3:11 PM
Status
Modified
Published
Jun 29, 2026, 11:16 PM
Modified
Oct 25, 2026, 9:10 PM