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 ]
| Vendor | Product | Versions |
|---|---|---|
| linux | linux_kernel | 8161239a8bcce9ad6b537c04a1fa3b5c68bae693, 8161239a8bcce9ad6b537c04a1fa3b5c68bae693, 8161239a8bcce9ad6b537c04a1fa3b5c68bae693, 8161239a8bcce9ad6b537c04a1fa3b5c68bae693, 8161239a8bcce9ad6b537c04a1fa3b5c68bae693, 8161239a8bcce9ad6b537c04a1fa3b5c68bae693, 8161239a8bcce9ad6b537c04a1fa3b5c68bae693, 8161239a8bcce9ad6b537c04a1fa3b5c68bae693, 2.6.39 |
Downstream vendors/products affected by this vulnerability
| Vendor | Product | Source | Confidence |
|---|---|---|---|
| open source | open source linux kernel | cert_advisory | 90% |
Updated description with details on the exploit's dependency on KASLR bypass techniques and added a new tag 'KASLR'.
Updated exploit availability to true and added new CVE IDs related to futex bugs.
Updated description with new details about GhostLock and marked the vulnerability as actively exploited.
Updated description with detailed exploit information, added new affected versions, marked as actively exploited, and included new CWE IDs and tags.
Updated description with details about GhostLock (CVE-2026-43499), changed severity to CRITICAL, and noted that it is actively exploited with an exploit available.
Updated severity to CRITICAL, added affected versions, and provided a new description detailing the vulnerability and its implications.
Initial creation
