rtmutex: Use waiter::task instead of current in remove_waiter()
8 public exploits exists; no exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 5%. Fixed in Kernel 6.1.175, Kernel 6.18.27, Kernel 7.0.4 and 12 more.
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 ]
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=2.6.39 <6.1.175, >=6.13 <6.18.27, >=6.19 <7.0.4, >=6.2 <6.6.140, >=6.7 <6.12.86, >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <3fb7394a837740770f0d6b4b30567e60786a63f2, >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <6d52dfcb2a5db86e346cf51f8fcf2071b8085166, >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <838ce5cb5d93c3ab8b27e75bc6ad905a94b752fd, >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <88614876370aac8ad1050ad785a4c095ba17ac11, >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <8a1fc8d698ac5e5916e3082a0f74450d71f9611f, >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <d8cce4773c2b23d819baf5abedc62f7b430e8745, >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <f3fa3424bceb128d2be4b3745506b22844b87db7, =2.6.39, >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <3bfdc63936dd4773109b7b8c280c0f3b5ae7d349 | 6.1.175, 6.18.27, 7.0.4, 6.6.140, 6.12.86, 3fb7394a837740770f0d6b4b30567e60786a63f2, 6d52dfcb2a5db86e346cf51f8fcf2071b8085166, 838ce5cb5d93c3ab8b27e75bc6ad905a94b752fd, 88614876370aac8ad1050ad785a4c095ba17ac11, 8a1fc8d698ac5e5916e3082a0f74450d71f9611f, d8cce4773c2b23d819baf5abedc62f7b430e8745, f3fa3424bceb128d2be4b3745506b22844b87db7, 3bfdc63936dd4773109b7b8c280c0f3b5ae7d349 |
| linux-kernel: Kernel | >=2.6.39 <5.10.261, >=5.11.0 <5.15.212, >=5.16.0 <6.1.175, >=6.13.0 <6.18.27, >=6.19.0 <7.0.4, >=6.2.0 <6.6.140, >=6.7.0 <6.12.86 | 5.10.261, 5.15.212, 6.1.175, 6.18.27, 7.0.4, 6.6.140, 6.12.86 |
Exploit evidence
8 public sources
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket