CVE-2026-43499: rtmutex: Use waiter::task instead of current in remove_waiter()
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 ]
Security readout for executives and security teams
A flaw in the Linux kernel's real-time mutex code could let a logged-in user crash the system or gain higher privileges. It affects a specific locking helper used during futex operations. Attackers need local access, and fixed kernels have been published on kernel.org, so the priority is patching internal Linux hosts on a normal cadence. Any Linux system running affected 6.1, 6.6, 6.12, 6.18, or 7.x kernel lines is exposed. The bug is reachable from user space through futex_requeue, so shared hosts, multi-tenant nodes, and workstations with untrusted local users carry the most risk. Fully patched stable branches (6.1.175, 6.6.140, 6.12.86, 6.18.27, 7.0.4, 7.1) are unaffected. Treat as a standard high-severity Linux kernel patch cycle. It is not a fire drill, but leaving it unpatched on shared or developer-facing Linux systems raises the risk of a local user escalating privileges. Fold into the next scheduled kernel maintenance window and confirm coverage across servers, containers hosts, and Linux endpoints. Mitigation focus: Upgrade to Linux stable 6.1.175, 6.6.140, 6.12.86, 6.18.27, 7.0.4, or 7.1 or later.; Track distribution kernel advisories and apply vendor-backported rtmutex fixes when available.; Restrict untrusted local accounts and container escape paths on shared Linux hosts until patched..
Prepared
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-43499 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
7Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.