Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
High

Linux kernel rtmutex remove_waiter() use-after-free in proxy-lock rollback

IdentifiersCVE-2026-43499CWE-416

CVE-2026-43499 is a Linux kernel rtmutex vulnerability in remove_waiter(). The bug arises because remove_waiter() is used both in normal slowlock paths and during proxy-lock rollback in rt_mutex_start_proxy_lock() when invoked from futex_requeue(). In the proxy-lock rollback case, waiter::task may differ from current, but the vulnerable code performed dequeue and related operations against current instead of waiter::task. According to the provided fix description, this causes the rbtree dequeue to occur without holding waiter::task::pi_lock, fails to clear the waiter task's pi_blocked_on state, and can leave a dangling pointer primed for use-after-free. It also causes rt_mutex_adjust_prio_chain() to operate on the wrong top-priority waiter task. The fix changes remove_waiter() and related operations to consistently use waiter::task instead of current.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can corrupt rtmutex waiter state and priority-inheritance bookkeeping in the kernel. The most explicit security consequence described in the provided content is that the waiter task's pi_blocked_on field may remain uncleared, leaving a dangling pointer that is primed for use-after-free. The flaw can also cause incorrect priority-chain adjustment and improper dequeue behavior without the correct pi_lock held. The supplied scoring and advisory context characterize this as a local vulnerability with high confidentiality, integrity, and availability impact on the affected system.

Mitigation

If you can’t patch tonight, do this now.

No specific workaround is provided in the supplied content short of applying the corrected kernel update. As a temporary risk-reduction measure, limit local untrusted code execution and restrict access to systems where attackers could exercise futex/rtmutex paths, but the authoritative mitigation in the provided material is patching.

Remediation

Patch, then assume compromise.

Apply a kernel update containing the upstream fix for CVE-2026-43499. The remediation described in the provided content is to modify remove_waiter() so that all related operations use waiter::task instead of current, including the rt_mutex_adjust_prio_chain() handling noted in the changelog. On SUSE systems, install the vendor kernel updates referenced in the advisories and reboot after patching.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LinuxLinux Kerneloperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity4

Community discussion across Reddit, Mastodon, and other social sources.