Tracker / CVE-2026-43499
CVE-2026-43499
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 ]
Prodotti e versioni affette
| linux | linux_kernel · 2.6.39 → 6.1.175 |
|---|---|
| linux | linux_kernel · 6.13 → 6.18.27 |
| linux | linux_kernel · 6.19 → 7.0.4 |
| linux | linux_kernel · 6.2 → 6.6.140 |
| linux | linux_kernel · 6.7 → 6.12.86 |