From 341efdc33b758cc9584921a8d4aae9585f24b4b1 Mon Sep 17 00:00:00 2001 From: Keenan Dong Date: Wed, 8 Apr 2026 16:46:00 +0800 Subject: [PATCH 1/2] rtmutex: Use waiter::task instead of current in remove_waiter() jira VULN-191592 cve CVE-2026-43499 commit-author Keenan Dong commit 3bfdc63936dd4773109b7b8c280c0f3b5ae7d349 upstream-diff | 3.10 has a monolithic kernel/rtmutex.c (not locking/rtmutex.c) and no scoped_guard() on el7, so the pi_lock section keeps raw_spin_lock_irqsave/irqrestore and the chain walk uses the 5-arg rt_mutex_adjust_prio_chain(). Functionally identical: remove_waiter() now operates on waiter->task. 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 ] Fixes: 8161239a8bcc ("rtmutex: Simplify PI algorithm and make highest prio task get lock") Reported-by: Yuan Tan Reported-by: Yifan Wu Reported-by: Juefei Pu Reported-by: Xin Liu Signed-off-by: Keenan Dong Signed-off-by: Thomas Gleixner Cc: stable@vger.kernel.org (cherry picked from commit 3bfdc63936dd4773109b7b8c280c0f3b5ae7d349) Signed-off-by: Sultan Alsawaf --- kernel/rtmutex.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/kernel/rtmutex.c b/kernel/rtmutex.c index 6131a046aab64..7387cdce05128 100644 --- a/kernel/rtmutex.c +++ b/kernel/rtmutex.c @@ -604,19 +604,22 @@ static void mark_wakeup_next_waiter(struct wake_q_head *wake_q, * * Must be called with lock->wait_lock held and * have just failed to try_to_take_rt_mutex(). + * + * When invoked from rt_mutex_start_proxy_lock() waiter::task != current ! */ static void remove_waiter(struct rt_mutex *lock, struct rt_mutex_waiter *waiter) { int first = (waiter == rt_mutex_top_waiter(lock)); struct task_struct *owner = rt_mutex_owner(lock); + struct task_struct *waiter_task = waiter->task; unsigned long flags; int chain_walk = 0; - raw_spin_lock_irqsave(¤t->pi_lock, flags); + raw_spin_lock_irqsave(&waiter_task->pi_lock, flags); rt_mutex_dequeue(lock, waiter); - current->pi_blocked_on = NULL; - raw_spin_unlock_irqrestore(¤t->pi_lock, flags); + waiter_task->pi_blocked_on = NULL; + raw_spin_unlock_irqrestore(&waiter_task->pi_lock, flags); if (!owner) return; @@ -649,7 +652,7 @@ static void remove_waiter(struct rt_mutex *lock, raw_spin_unlock(&lock->wait_lock); - rt_mutex_adjust_prio_chain(owner, 0, lock, NULL, current); + rt_mutex_adjust_prio_chain(owner, 0, lock, NULL, waiter_task); raw_spin_lock(&lock->wait_lock); } From 4c55a2663c86b29e76ca4ebffded498f6b4a667a Mon Sep 17 00:00:00 2001 From: Davidlohr Bueso Date: Thu, 7 May 2026 04:29:13 -0700 Subject: [PATCH 2/2] locking/rtmutex: Skip remove_waiter() when waiter is not enqueued cve CVE-2026-53163 commit-author Davidlohr Bueso commit 40a25d59e85b3c8709ac2424d44f65610467871e upstream-diff | 3.10 monolithic kernel/rtmutex.c: both hunks land in the one file, and the ret guard sits in the unsplit rt_mutex_start_proxy_lock() as if (unlikely(ret < 0)). Both hunks are defensive no-ops here (waiter->task is always armed and ret is only ever 0 or <0), carried for upstream fidelity. syzbot triggered the following splat in remove_waiter() via FUTEX_CMP_REQUEUE_PI: KASAN: null-ptr-deref in range [0x0000000000000a88-0x0000000000000a8f] class_raw_spinlock_constructor remove_waiter+0x159/0x1200 kernel/locking/rtmutex.c:1561 rt_mutex_start_proxy_lock+0x103/0x120 futex_requeue+0x10e4/0x20d0 __x64_sys_futex+0x34f/0x4d0 task_blocks_on_rt_mutex() does not arm the waiter upon deadlock detection, leaving waiter->task nil, where 3bfdc63936dd ("rtmutex: Use waiter::task instead of current in remove_waiter()") made this fatal. Furthermore, rt_mutex_start_proxy_lock() should not be calling into remove_waiter() upon a successfully grabbing the rtmutex. 1a1fb985f2e2 ("futex: Handle early deadlock return correctly"), moved the remove_waiter() out of __rt_mutex_start_proxy_lock() (where 'ret' was only ever 0 or < 0) into the wrapper. Tighten this check to account for try_to_take_rt_mutex(). Fixes: 3bfdc63936dd ("rtmutex: Use waiter::task instead of current in remove_waiter()") Reported-by: syzbot+78147abe6c524f183ee9@syzkaller.appspotmail.com Signed-off-by: Davidlohr Bueso Signed-off-by: Thomas Gleixner Cc: stable@vger.kernel.org Closes: https://lore.kernel.org/all/69f114ac.050a0220.ac8b.0003.GAE@google.com/ Link: https://patch.msgid.link/20260507112913.1019537-1-dave@stgolabs.net (cherry picked from commit 40a25d59e85b3c8709ac2424d44f65610467871e) Signed-off-by: Sultan Alsawaf --- kernel/rtmutex.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/kernel/rtmutex.c b/kernel/rtmutex.c index 7387cdce05128..520d0e2ed4088 100644 --- a/kernel/rtmutex.c +++ b/kernel/rtmutex.c @@ -616,6 +616,9 @@ static void remove_waiter(struct rt_mutex *lock, unsigned long flags; int chain_walk = 0; + if (!waiter_task) /* never enqueued */ + return; + raw_spin_lock_irqsave(&waiter_task->pi_lock, flags); rt_mutex_dequeue(lock, waiter); waiter_task->pi_blocked_on = NULL; @@ -1096,7 +1099,7 @@ int rt_mutex_start_proxy_lock(struct rt_mutex *lock, ret = 0; } - if (unlikely(ret)) + if (unlikely(ret < 0)) remove_waiter(lock, waiter); raw_spin_unlock(&lock->wait_lock);