Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-11812Published 2026-08-10

CVE-2026-11812 — zephyrproject zephyr

low

As of 2026-08-10, CVE-2026-11812 is a LOW-severity vulnerability in zephyrproject zephyr, CVSS v3.1 2.5, EPSS 0.0% (21.6th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-11812 as of 2026-08-10; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
2.5/10Low
EPSS
0.0%Higher than 21.6% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
2.1/10Threadlinqs triage score
Published
CVSS v3.1 2.5 (LOW) · EPSS 0.0% (higher than 21.6% of all scored CVEs) · Priority 2.1/10 · Published 2026-08-10

Last updated:

What is CVE-2026-11812?

The UpdateHub management subsystem (subsys/mgmt/updatehub/updatehub.c) drives every update operation through a single file-scope ctx structure that holds the CoAP block context, payload buffer, status code, socket, and a one-element poll-fd array fds[1]. Access to ctx was not serialized, and prepare_fds() wrote ctx.fds[ctx.nfds] and incremented ctx.nfds with no bounds check. Two independent paths mutate ctx concurrently: the background autohandler running on the system workqueue, and user-triggered operations reached through the updatehub run shell command, direct API calls, or — since the operations are exposed as syscalls — userspace threads. When a second flow enters prepare_fds() while ctx.nfds is already 1, the write lands one element past the array; by struct layout it overlaps the adjacent ctx.sock/ctx.nfds members. More broadly, the unsynchronized sharing lets two flows interleave connection setup and teardown, double-closing a socket descriptor or scribbling the shared buffers. The result is corruption of the update subsystem's internal state and denial of service of the firmware-update path; the out-of-bounds write is contained within the ctx structure and there is no demonstrated path to memory outside it or to code execution. Triggering requires a local actor able to invoke update operations (or, with CONFIG_USERSPACE, an unprivileged userspace thread) and to win a timing race against the background handler; remote peers cannot control the race timing. The fix serializes the entry points with a mutex and adds a bounds check to prepare_fds().

The record classifies CVE-2026-11812 under weakness class CWE-362. Its CVSS v3 base vector states that the flaw requires local access to the host, needs low-privilege credentials, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 101 days ago.

Severity and exploitation probability

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

Is CVE-2026-11812 being exploited?

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

Affected products and versions

How to fix CVE-2026-11812

Patch reference: https://github.com/zephyrproject-rtos/zephyr/commit/551d3f92b36e9604f039101c4e4f623682d02159. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-11812

No threat campaign in the Threadlinqs corpus currently references CVE-2026-11812, 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. This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Other references