CVE 7.8 HIGH

rtmutex: Use waiter::task instead of current in remove_waiter()_CVE-2026-43499

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

Description

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 ]

Basic Information

ID CVE-2026-43499
Source Linux
Published May 21, 2026 at 12:17
Modified May 30, 2026 at 10:45

Affected Product

Vendor Linux
Product Linux
Version 8161239a8bcce9ad6b537c04a1fa3b5c68bae693
Affected Versions Linux Linux 8161239a8bcce9ad6b537c04a1fa3b5c68bae693
Linux Linux 8161239a8bcce9ad6b537c04a1fa3b5c68bae693
Linux Linux 8161239a8bcce9ad6b537c04a1fa3b5c68bae693
Linux Linux 8161239a8bcce9ad6b537c04a1fa3b5c68bae693
Linux Linux 8161239a8bcce9ad6b537c04a1fa3b5c68bae693
Linux Linux 2.6.39

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.