VULNERABILITY INTELLIGENCE
CVE-2026-43499
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 ]
Weakness classification
- nvd@nist.gov: CWE-416
- 134c704f-9b21-4f2e-91b3-4a467353bcc0: CWE-416
Primary references
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67 — Patch
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67 — Patch
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67 — Patch
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67 — Patch
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67 — Patch
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67 — Patch
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- af854a3a-2127-422b-91ae-364da2661108
- 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
- 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
- 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e