Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-10681Published 2026-07-25

CVE-2026-10681 — zephyrproject zephyr

medium

As of 2026-07-25, CVE-2026-10681 is a MEDIUM-severity vulnerability in zephyrproject zephyr, CVSS v3.1 6.5, EPSS 0.0% (20.5th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-10681 as of 2026-07-25; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
6.5/10Medium
EPSS
0.0%Higher than 20.5% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
4.1/10Threadlinqs triage score
Published
CVSS v3.1 6.5 (MEDIUM) · EPSS 0.0% (higher than 20.5% of all scored CVEs) · Priority 4.1/10 · Published 2026-07-25

Last updated:

What is CVE-2026-10681?

In Zephyr's userspace dynamic-objects subsystem, thread_idx_alloc() in kernel/userspace/userspace.c allocated a new thread permission index from the global _thread_idx_map[] bitmap without holding lists_lock. On SMP systems, two user-mode threads invoking the k_object_alloc(K_OBJ_THREAD) syscall concurrently can both observe the same low free bit, perform the same non-atomic RMW to clear it, and return the identical tidx. The two newly created K_OBJ_THREAD objects are then assigned the same thread_id, so the two user threads alias a single bit position in every kernel object's perms[] bitfield: any subsequent grant of access on a kernel object to one thread is implicitly a grant to the other, defeating userspace ACL isolation. A secondary lost-update window between the unlocked &=~BIT() in alloc and the locked |= BIT() in thread_idx_free() can also leak entries from the thread-index pool. The defect is reachable from any user-mode thread via the unrestricted __syscall k_object_alloc and is gated on CONFIG_USERSPACE, CONFIG_DYNAMIC_OBJECTS, and CONFIG_SMP. The flaw was introduced when the per-thread permission index was added in 2018 and is present in every release up to and including v4.4.0. Fixed by holding lists_lock across the bitmap RMW and the permissions clear (and inlining the obj_list traversal that previously took the lock itself).

The record classifies CVE-2026-10681 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, and has high impact on confidentiality, integrity. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 117 days ago.

Severity and exploitation probability

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

Is CVE-2026-10681 being exploited?

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

Affected products and versions

How to fix CVE-2026-10681

Patch reference: https://github.com/zephyrproject-rtos/zephyr/commit/862ea2fbbeb2ccdf8ff994b03e2e3b4405f2c37d. 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-10681

No threat campaign in the Threadlinqs corpus currently references CVE-2026-10681, 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