Zephyr RTOS
CVE-2026-10648
MEDIUM
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain serial/UART or shell-console link access
-
DeliveryTransmit rapid SMP fragment flood
-
ExploitExhaust 4-entry MCUmgr buffer pool
-
Executionsmp_packet_alloc() returns NULL
-
Persistnet_buf_reset() writes through NULL pointer
-
ImpactProcessor fault and device crash
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A10:2025 - Mishandling of Exceptional Conditions
ASVS 5.0
V16 - Security Logging and Error Handling Null pointer safety, defensive checks
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to have access to the MCUmgr serial, UART, or shell-console transport link on the target device - specifically, one of the three affected transport drivers (smp_uart.c, smp_raw_uart.c, or smp_shell.c) must be compiled into the firmware. The device must run Zephyr v4.4.0 with MCUmgr serial transport enabled, which is a non-default feature that must be explicitly included in the board or application configuration. The default buffer pool size of 4 (CONFIG_MCUMGR_TRANSPORT_NETBUF_COUNT) makes exhaustion trivially achievable. Exploitation is limited by: the requirement for physical or local access to the serial/UART/console interface (CVSS AV:L), the need for MCUmgr transport to be enabled in the specific firmware build, and restriction to Zephyr v4.4.0 builds prior to the fix commit. No network-based exploitation path exists; an attacker must be physically present or have shell-level access to the host connected to the device's console port. |
| Impact | The CVSS 3.1 base score of 6.2 (Medium) with vector AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H accurately reflects the constrained attack surface: exploitation requires physical or logical presence on the serial or shell-console link, which substantially limits the attacker population compared to network-reachable vulnerabilities. Attack complexity is genuinely low once the interface is accessible - flooding with SMP packets until the 4-entry pool is exhausted is trivial. The Availability:High rating is warranted because the result is a hard device fault and reset, not a graceful degradation. There is no confidentiality or integrity impact. No EPSS data was provided in the intelligence set, and the vulnerability carries no CISA KEV listing and no known public POC. The primary real-world risk is physical-access adversaries or insider threats targeting embedded/IoT devices running MCUmgr-enabled Zephyr v4.4.0. The extremely small buffer pool (4 entries) means the denial-of-service condition is reliably reproducible without sophisticated tooling. For devices in safety-critical or always-available roles (industrial controls, medical devices), the crash impact may exceed what the medium CVSS score implies. |
| Exploit ScenarioDerived | An attacker with physical or logical access to a UART or shell-console port on a Zephyr v4.4.0 device rapidly sends a stream of MCUmgr SMP packet fragments, driving all four entries in the shared MCUmgr buffer pool to allocated-but-not-freed state. The next fragment allocation returns NULL, mcumgr_serial_process_frag() calls net_buf_reset() on it without checking, and the resulting NULL pointer write causes a processor exception, crashing and resetting the device. No exploit code has been publicly identified, but the attack requires only a serial terminal and knowledge of the SMP packet format. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 29, 2026
Denial of service in Zephyr RTOS v4.4.0 allows an attacker with access to a serial, UART, or shell-console interface to crash an affected embedded device by exhausting the MCUmgr shared buffer pool and triggering a NULL pointer dereference. The defect in mcumgr_serial_process_frag() (CWE-476) was introduced during the MCUmgr rework and manifests in default builds where assertion checks are compiled out, making the write-through-NULL a hard fault rather than a caught assertion. No public exploit has been identified at time of analysis and no CISA KEV listing exists, but exploitation is straightforward for any attacker with interface access.
RemediationAI
The upstream fix is available as commit 6f363ec6f7fd6ae9ed7ca2ae66fd9c82dce31c59 in the Zephyr project repository (https://github.com/zephyrproject-rtos/zephyr/commit/6f363ec6f7fd6ae9ed7ca2ae66fd9c82dce31c59); a patched tagged release version has not been independently confirmed from available data - project maintainers should monitor the Zephyr release channel for a version incorporating this fix. Developers building from source should cherry-pick or rebase to include the fix commit. As a compensating control, increasing CONFIG_MCUMGR_TRANSPORT_NETBUF_COUNT above the default of 4 raises the number of floods required to exhaust the pool, but does not eliminate the NULL dereference - it only makes the condition harder to trigger transiently. Disabling MCUmgr serial/UART/shell transport entirely (by removing CONFIG_MCUMGR_TRANSPORT_UART, CONFIG_MCUMGR_TRANSPORT_UDP_SMP, or CONFIG_MCUMGR_TRANSPORT_SHELL from the build configuration) is an effective workaround if the management interface is not required in production, with the trade-off of losing over-the-air firmware update and management capability. Physical access controls on serial/console ports reduce the attacker population but are not a software mitigation. The security advisory is at https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-j64f-h3ww-f32c.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Zephyr RTOS (cpe:2.3:a:zephyrproject:zephyr:*:*:*:*:*:*:*:*) is an open-source real-time operating system targeting resource-constrained embedded and IoT devices. Its MCUmgr subsystem provides a management protocol (SMP) over multiple transports including UART (smp_uart.c, smp_raw_uart.c) and shell-console (smp_shell.c). Each incoming SMP packet fragment triggers a buffer allocation from a shared kernel buffer pool sized by CONFIG_MCUMGR_TRANSPORT_NETBUF_COUNT (default 4). The root cause is CWE-476 (NULL Pointer Dereference): mcumgr_serial_process_frag() invokes net_buf_reset() on the pointer returned by smp_packet_alloc() without first checking whether the allocation succeeded. smp_packet_alloc() uses net_buf_alloc(K_NO_WAIT), which returns NULL immediately when the pool is exhausted rather than blocking. Because __ASSERT_NO_MSG is compiled out in default Zephyr builds, net_buf_simple_reset proceeds to write buf->len = 0 and buf->data = buf->__buf through the NULL pointer, causing a processor fault and device reset. The fix, available in upstream commit 6f363ec6, relocates the NULL guard ahead of the reset call.
Know when Zephyr gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Local vector confirmed by serial/UART/console-only attack path; PR:N because no authentication is enforced on the physical link itself; A:H for hard device fault; no confidentiality or integrity impact.
Primary rating from Vendor (zephyr).
CVSS VectorNVD
Lifecycle Timeline
1DescriptionNVD
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A null pointer dereference occurs when a program attempts to access memory through a pointer that has been set to NULL (address 0x0).
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Affected Products (CPE)NVD
Potential off-by-one buffer overflow vulnerability in the Zephyr fuse file system. Rated critical severity (CVSS 10.0),
An out-of-bounds write in the Zephyr RTOS DNS resolver (dns_unpack_name()) lets a crafted DNS response corrupt memory on
Possible variant of CVE-2021-3434 in function le_ecred_reconf_req. Rated critical severity (CVSS 9.8), this vulnerabilit
Unchecked user input length in /subsys/net/l2/wifi/wifi_shell.c can cause buffer overflows. Rated critical severity (CVS
Potential buffer overflow vulnerability in the Zephyr CAN bus subsystem. Rated critical severity (CVSS 9.8), this vulner
Integer Underflow in 6LoWPAN IPHC Header Uncompression in Zephyr. Rated critical severity (CVSS 9.8), this vulnerability
Buffer overflow in Zephyr USB DFU DNLOAD. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable
DOS: Incorrect 802154 Frame Validation for Omitted Source / Dest Addresses. Rated critical severity (CVSS 9.8), this vul
zephyr-rtos version 1.12.0 contains a NULL base pointer reference vulnerability in sys_ring_buf_put(), sys_ring_buf_get(
Potential buffer overflow vulnerabilities n the Zephyr Bluetooth subsystem. Rated critical severity (CVSS 9.6), this vul
The documentation specifies that the BT_GATT_PERM_READ_LESC and BT_GATT_PERM_WRITE_LESC defines for a Bluetooth characte
Potential buffer overflows in the Bluetooth subsystem due to asserts being disabled in /subsys/bluetooth/host/hci_core.c
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB