rtmutex: Use waiter::task instead of current in remove_waiter()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.261, 5.15.212, 6.1.175, 6.6.140, 6.12.86, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
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 ]
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 · fixed in f3fa3424bceb128d2be4b3745506b22844b87db7; From 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 · fixed in 838ce5cb5d93c3ab8b27e75bc6ad905a94b752fd; From 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 · fixed in d8cce4773c2b23d819baf5abedc62f7b430e8745; From 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 · fixed in 8a1fc8d698ac5e5916e3082a0f74450d71f9611f; From 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 · fixed in 6d52dfcb2a5db86e346cf51f8fcf2071b8085166; From 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 · fixed in 3fb7394a837740770f0d6b4b30567e60786a63f2; From 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 · fixed in 88614876370aac8ad1050ad785a4c095ba17ac11; From 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 · fixed in 3bfdc63936dd4773109b7b8c280c0f3b5ae7d349
- Linux Linux
2.6.39
- KernelLinux
From 2.6.39 · fixed in 5.10.261; From 5.11.0 · fixed in 5.15.212; From 5.16.0 · fixed in 6.1.175; From 6.2.0 · fixed in 6.6.140; From 6.7.0 · fixed in 6.12.86; From 6.13.0 · fixed in 6.18.27; From 6.19.0 · fixed in 7.0.4
References 8
git.kernel.org
- stable/c/f3fa3424bceb128d2be4b3745506b22844b87db7
- stable/c/838ce5cb5d93c3ab8b27e75bc6ad905a94b752fd
- stable/c/d8cce4773c2b23d819baf5abedc62f7b430e8745
- stable/c/8a1fc8d698ac5e5916e3082a0f74450d71f9611f
- stable/c/6d52dfcb2a5db86e346cf51f8fcf2071b8085166
- stable/c/3fb7394a837740770f0d6b4b30567e60786a63f2
- stable/c/88614876370aac8ad1050ad785a4c095ba17ac11
- stable/c/3bfdc63936dd4773109b7b8c280c0f3b5ae7d349