CVE-2026-43499
🟠 MediumLinux kernel rtmutex and futex code. The record also carries three Siemens ProductCERT advisories, so the flaw is being tracked into Siemens products as well as distributions · Vulnerable from 2.6.39 onward (commit 8161239a). Fixed in 5.10.261, 5.15.212, 6.1.175, 6.6.140, 6.12.86, 6.18.27, 7.0.4 and 7.1 mainline
92.81th percentile
Exploitation
Timeline
- 21/05/2026CVE record published (CVE List)
Risk
remove_waiter() used the current task instead of the waiter's task during proxy-lock rollback from a futex requeue, corrupting the rbtree without the right lock and leaving a dangling pi_blocked_on pointer)Fix
Official description
In the Linux kernel, the following vulnerability has been resolved: rtmutex: Use waiter::task instead of current in remove_waiter() remove_waiter() is used by the slowlock paths, but it is also used for proxy-lock rollback in rt_mutex_start_proxy_lock() when invoked from futex_requeue(). In the latter case waiter::task is not current, but remove_waiter() operates on current for the dequeue operation. That results in several problems: 1) the rbtree dequeue happens without waiter::task::pi_lock being held 2) the waiter task's pi_blocked_on state is not cleared, which leaves a dangling pointer primed for UAF around. 3) rt_mutex_adjust_prio_chain() operates on the wrong top priority waiter task Use waiter::task instead of current in all related operations in remove_waiter() to cure those problems. [ tglx: Fixup rt_mutex_adjust_prio_chain(), add a comment and amend the changelog ]
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H