Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-10648Published 2026-06-29

CVE-2026-10648 — zephyrproject zephyr

medium

As of 2026-06-30, CVE-2026-10648 is a MEDIUM-severity vulnerability in zephyrproject zephyr, CVSS v3.1 6.2, EPSS 0.1% (1.7th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-10648 as of 2026-06-30; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
6.2/10Medium
EPSS
0.1%Higher than 1.7% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
3.2/10Threadlinqs triage score
Published
Updated 2026-06-30
CVSS v3.1 6.2 (MEDIUM) · EPSS 0.1% (higher than 1.7% of all scored CVEs) · Priority 3.2/10 · Published 2026-06-29

Last updated:

What is CVE-2026-10648?

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.

The record classifies CVE-2026-10648 under weakness class CWE-476. Its CVSS v3 base vector states that the flaw requires local access to the host, needs no prior authentication, needs no user interaction, and has high impact on availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 98 days ago.

Severity and exploitation probability

CVSS v3.1 base score
6.2 — MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (FIRST)
0.1% probability of exploitation in the next 30 days, higher than 1.7% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
3.2/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-06-29, last modified 2026-06-30

Is CVE-2026-10648 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-10648

No vendor patch reference has been recorded for CVE-2026-10648 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-10648

No threat campaign in the Threadlinqs corpus currently references CVE-2026-10648, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, FIRST EPSS. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Other references