SECUFOCUSNOW
Home›CVE index›CVE-2026-43499
Review reviewHigh

CVE-2026-43499

Linux Linux, linux kernel

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...

CVSS
7.8
EPSS
0.73%
50.5% percentile
CISA KEV
Not listed
Published
2026.05.21
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.73%
Technical severityCVSS 7.8

Vulnerability overview

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...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 < f3fa3424bceb128d2be4b3745506b22844b87db7, >= 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 < 838ce5cb5d93c3ab8b27e75bc6ad905a94b752fd, >= 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 < d8cce4773c2b23d819baf5abedc62f7b430e8745, >= 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 < 8a1fc8d698ac5e5916e3082a0f74450d71f9611f, >= 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 < 6d52dfcb2a5db86e346cf51f8fcf2071b8085166, >= 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 < 3fb7394a837740770f0d6b4b30567e60786a63f2, >= 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 < 88614876370aac8ad1050ad785a4c095ba17ac11, >= 8161239a8bcce9ad6b537c04a1fa3b5c68bae693 < 3bfdc63936dd4773109b7b8c280c0f3b5ae7d349, >= 2.6.39, >= 2.6.39 < 6.1.175, >= 6.2 < 6.6.140, >= 6.7 < 6.12.86, >= 6.13 < 6.18.27, >= 6.19 < 7.0.4
Fixed versions
6.1.175, 6.6.140, 6.12.86, 6.18.27, 7.0.4

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-416
CVE-2026-43499 — Linux Linux, linux kernel | SECUFOCUS NOW