Skip to content
Noroxi
CVE-2026-43499· NVD / CVE Program· CNA Linux

rtmutex: Use waiter::task instead of current in remove_waiter()

Noroxi assessment

Priority: Monitor (action score 31/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.78% (FIRST EPSS); higher than 55.3% of all records.
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 3bfdc63936dd4773109b7b8c280c0f3b5ae7d349, 3fb7394a837740770f0d6b4b30567e60786a63f2, 6d52dfcb2a5db86e346cf51f8fcf2071b8085166.

Low priority for now. Upgrade to Linux Linux 3bfdc63936dd4773109b7b8c280c0f3b5ae7d349, 3fb7394a837740770f0d6b4b30567e60786a63f2, 6d52dfcb2a5db86e346cf51f8fcf2071b8085166 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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 ]

HighCVSS 7.8 · v3.1—Proof of concept Fix available
Published
May 21, 2026
Updated
Oct 15, 2026
EPSS
0.7% · 55th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.7%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-43499

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel2.6.39 and later · before 6.1.175
  • linux linux kernel6.2 and later · before 6.6.140
  • linux linux kernel6.7 and later · before 6.12.86
  • linux linux kernel6.13 and later · before 6.18.27
  • linux linux kernel6.19 and later · before 7.0.4

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.39affected
    • 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 and later · before f3fa3424bceb128d2be4b3745506b22844b87db7affected · git
    • 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 and later · before 838ce5cb5d93c3ab8b27e75bc6ad905a94b752fdaffected · git
    • 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 and later · before d8cce4773c2b23d819baf5abedc62f7b430e8745affected · git
    • 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 and later · before 8a1fc8d698ac5e5916e3082a0f74450d71f9611faffected · git
    • 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 and later · before 6d52dfcb2a5db86e346cf51f8fcf2071b8085166affected · git
    • 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 and later · before 3fb7394a837740770f0d6b4b30567e60786a63f2affected · git
    • 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 and later · before 88614876370aac8ad1050ad785a4c095ba17ac11affected · git
    • 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 and later · before 3bfdc63936dd4773109b7b8c280c0f3b5ae7d349affected · git
    • before 2.6.39not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.33.1.el10_26.12.0-211.33.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now
  • CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV
    77This week
  • CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV
    77This week
  • CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV
    77This week

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3bfdc63936dd4773109b7b8c280c0f3b5ae7d349Vendor (CNA)
Linux Linux3fb7394a837740770f0d6b4b30567e60786a63f2Vendor (CNA)
Linux Linux6d52dfcb2a5db86e346cf51f8fcf2071b8085166Vendor (CNA)
Linux Linux838ce5cb5d93c3ab8b27e75bc6ad905a94b752fdVendor (CNA)
Linux Linux88614876370aac8ad1050ad785a4c095ba17ac11Vendor (CNA)
Linux Linux8a1fc8d698ac5e5916e3082a0f74450d71f9611fVendor (CNA)
Linux Linuxd8cce4773c2b23d819baf5abedc62f7b430e8745Vendor (CNA)
Linux Linuxf3fa3424bceb128d2be4b3745506b22844b87db7Vendor (CNA)
almalinux:kernel5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-687.25.1.el9_8 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.176-1 · Debian:12Package registry (OSV)
opensuse:kernel-source7.0.10-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:kernel0:6.12.0-231.16.el10nv · Red Hat:enterprise_linux_nvidia:10::el10Package registry (OSV)
red hat:kernel-64k0:6.12.0-231.16.el10nv · Red Hat:enterprise_linux_nvidia:10::el10Package registry (OSV)
red hat:kernel-64k-core0:6.12.0-231.16.el10nv · Red Hat:enterprise_linux_nvidia:10::el10Package registry (OSV)
red hat:kernel-64k-debug0:6.12.0-231.16.el10nv · Red Hat:enterprise_linux_nvidia:10::el10Package registry (OSV)
red hat:kernel-64k-debug-core0:6.12.0-231.16.el10nv · Red Hat:enterprise_linux_nvidia:10::el10Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-231.16.el10nv · Red Hat:enterprise_linux_nvidia:10::el10Package registry (OSV)
red hat:kernel-64k-debug-modules0:6.12.0-231.16.el10nv · Red Hat:enterprise_linux_nvidia:10::el10Package registry (OSV)
red hat:kernel-64k-debug-modules-core0:6.12.0-231.16.el10nv · Red Hat:enterprise_linux_nvidia:10::el10Package registry (OSV)

+17

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×50

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:1622026-06-27
Proof-of-concept repository on GitHubstars:12026-07-08
Proof-of-concept repository on GitHubstars:92026-07-08
Proof-of-concept repository on GitHubstars:112026-07-09
Proof-of-concept repository on GitHubstars:12026-07-09
Proof-of-concept repository on GitHubstars:662026-07-09
Proof-of-concept repository on GitHubstars:12026-07-10
Proof-of-concept repository on GitHubstars:02026-07-10
Proof-of-concept repository on GitHubstars:2562026-07-12
Proof-of-concept repository on GitHubstars:32026-07-12
Proof-of-concept repository on GitHubstars:4222026-07-12
Proof-of-concept repository on GitHubstars:1002026-07-12

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+36 d
  3. TodayOct 17, 2026+149 d
EPSS, last 120 days+1% in 7 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records