CVE-2026-12365

MEDIUM
MEDIUM Priority: 0.01 BB Relevance: 27/100
Published: 2026-08-14 Modified: 2026-11-04 First seen: 2026-11-04 Status: active

Attack Surface

No Interaction

CVSS Vector Breakdown

AV: Local
AC: High
PR: Low
UI: None
S: Unchanged
C: Low
I: Low
A: High

Description

A use-after-free exists in the Zephyr second-generation work queue (kernel/work.c) in the handling of delayable work timeouts. When a delayable work item's timeout has been dequeued and its handler work_timeout() is in flight (blocked acquiring the work-queue spinlock), a concurrent cancellation does not wait for that handler to finish. In unschedule_locked() the pre-fix code called z_abort_timeout(), which for an already-announcing record returns -EINVAL without removing it; cancel_async_locked() then observes the work as idle, so even k_work_cancel_delayable_sync() and k_work_flush_delayable() return without blocking on the in-flight handler. Because those are the APIs the kernel header documents as the safe way to cancel before freeing a k_work_delayable, a caller that frees the object immediately after a successful sync cancel can race the still-pending handler. work_timeout() subsequently dereferences the freed record: it reads to->dticks via z_is_timeout_handler_canceled() and, if the freed slot has been reused so the bail check fails, performs a read-modify-write of wp->flags (K_WORK_DELAYED_BIT) and submits work against a stale dw->queue pointer — a use-after-free read and write. The k_work API is kernel-mode only (no __syscall entry point), so this is a kernel-internal concurrency defect rather than a userspace privilege escalation. Triggering it requires an SMP build and a subsystem that schedules and then frees (or reschedules) a delayable work item in the narrow window while its timeout is announcing; an attacker able to influence the timing of such teardown (for example via connection churn driving subsystem timers) has a plausible but probabilistic path. The impact is kernel memory corruption or crash (denial of service). The fix makes unschedule_locked() wait, by spinning on z_try_abort_timeout() returning -EAGAIN while releasing and re-acquiring the work spinlock, until any in-flight handler completes before returning, and switches work_timeout() to atomic K_WORK_DELAYED_BIT ownership. This closes both the free-then-handler use-after-free and the related reschedule early-fire race.

Weakness Classification (1)

Affected Software (1)

VendorProductVersion
zephyrproject zephyr 2.6.0 < 4.5.0

Bug Bounty Relevance

27 / 100
✓ No user interaction

CVSS Score

5.8 / 10.0 v3.1
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H

EPSS — Exploitation Probability

0.13%
Raw Score 0.001270
Percentile 2.4%
Date 2026-11-14

EPSS Trend

2026-11-14
0.00127
2026-11-13
0.00127
2026-11-12
0.00127
2026-11-10
0.00127
2026-11-09
0.00127
2026-11-08
0.00127
2026-11-07
0.00127
2026-11-06
0.00127
2026-11-05
0.00127
2026-11-04
0.00127
2026-11-03
0.00127

Intelligence Sources

mitre ref →