Answer in brief
CVE-2026-43499 records a High severity (CVSS 7.8) vulnerability in rtmutex: Use waiter::task instead of current in remove_waiter(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-43499 records a High severity (CVSS 7.8) vulnerability in rtmutex: Use waiter::task instead of current in remove_waiter(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <f3fa3424bceb128d2be4b3745506b22844b87db7 || >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <838ce5cb5d93c3ab8b27e75bc6ad905a94b752fd || >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <d8cce4773c2b23d819baf5abedc62f7b430e8745 || >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <8a1fc8d698ac5e5916e3082a0f74450d71f9611f || >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <6d52dfcb2a5db86e346cf51f8fcf2071b8085166 || >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <3fb7394a837740770f0d6b4b30567e60786a63f2 || >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <88614876370aac8ad1050ad785a4c095ba17ac11 || >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <3bfdc63936dd4773109b7b8c280c0f3b5ae7d349 | f3fa3424bceb128d2be4b3745506b22844b87db7, 838ce5cb5d93c3ab8b27e75bc6ad905a94b752fd, d8cce4773c2b23d819baf5abedc62f7b430e8745, 8a1fc8d698ac5e5916e3082a0f74450d71f9611f, 6d52dfcb2a5db86e346cf51f8fcf2071b8085166, 3fb7394a837740770f0d6b4b30567e60786a63f2, 88614876370aac8ad1050ad785a4c095ba17ac11, 3bfdc63936dd4773109b7b8c280c0f3b5ae7d349 |
| Linux/Linuxgeneric | 2.6.39 | Not reported |
Published upstream
May 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 26, 2026
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 ]
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <f3fa3424bceb128d2be4b3745506b22844b87db7 || >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <838ce5cb5d93c3ab8b27e75bc6ad905a94b752fd || >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <d8cce4773c2b23d819baf5abedc62f7b430e8745 || >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <8a1fc8d698ac5e5916e3082a0f74450d71f9611f || >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <6d52dfcb2a5db86e346cf51f8fcf2071b8085166 || >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <3fb7394a837740770f0d6b4b30567e60786a63f2 || >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <88614876370aac8ad1050ad785a4c095ba17ac11 || >=8161239a8bcce9ad6b537c04a1fa3b5c68bae693 <3bfdc63936dd4773109b7b8c280c0f3b5ae7d349 | f3fa3424bceb128d2be4b3745506b22844b87db7, 838ce5cb5d93c3ab8b27e75bc6ad905a94b752fd, d8cce4773c2b23d819baf5abedc62f7b430e8745, 8a1fc8d698ac5e5916e3082a0f74450d71f9611f, 6d52dfcb2a5db86e346cf51f8fcf2071b8085166, 3fb7394a837740770f0d6b4b30567e60786a63f2, 88614876370aac8ad1050ad785a4c095ba17ac11, 3bfdc63936dd4773109b7b8c280c0f3b5ae7d349 |
| Linux/Linuxgeneric | 2.6.39 | Not reported |
Published upstream
May 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 26, 2026
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 ]
Quoted source text, attributed separately from HOL analysis.