Look up another CVE · open CVE-2026-53163 in the interactive tracker
CVE-2026-53163
locking/rtmutex: Skip remove_waiter() when waiter is not enqueued
Published 2026-06-25 (4 months ago) by the Linux kernel CNA. Subsystem kernel/locking. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-53163 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixedDLA-4688-1 · 2026-07-18 · text | 6.1.177-1 | Update the kernel and reboot. DLA-4688-1 shipped the fix on 2026-07-18, in 6.1.177-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixedDSA-6381-1 · 2026-07-05 · text | 6.12.95-1 | Update the kernel and reboot. DSA-6381-1 shipped the fix on 2026-07-05, in 6.12.95-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.0.13-1 | Update the kernel and reboot. Fixed in 7.0.13-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.0.13-1 | Update the kernel and reboot. Fixed in 7.0.13-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
syzbot triggered the following splat in remove_waiter() via FUTEX_CMP_REQUEUE_PI: KASAN: null-ptr-deref in range [0x0000000000000a88-0x0000000000000a8f] class_raw_spinlock_constructor remove_waiter+0x159/0x1200 kernel/locking/rtmutex.c:1561 rt_mutex_start_proxy_lock+0x103/0x120 futex_requeue+0x10e4/0x20d0 __x64_sys_futex+0x34f/0x4d0 task_blocks_on_rt_mutex() does not arm the waiter upon deadlock detection, leaving waiter->task nil, where 3bfdc63936dd ("rtmutex: Use waiter::task instead of current in remove_waiter()") made this fatal. Furthermore, rt_mutex_start_proxy_lock() should not be calling into remove_waiter() upon a successfully grabbing the rtmutex. 1a1fb985f2e2 ("futex: Handle early deadlock return correctly"), moved the remove_waiter() out of __rt_mutex_start_proxy_lock() (where 'ret' was only ever 0 or < 0) into the wrapper. Tighten this check to account for try_to_take_rt_mutex().
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
kernel/locking/rtmutex.c
kernel/locking/rtmutex_api.c
- What this is
- LOCKING PRIMITIVESMAINTAINERS section matched on kernel/locking/ · linux-kernel@vger.kernel.org · Maintained
Check it on the machine
grep -w CONFIG_RT_MUTEXES /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
Show whether Debian builds this, per release
Debian builds this code. Every release below compiles the affected file into the kernels it ships.
- bookworm, trixie, forky, sidy
- y
- built into the kernel image on every flavour - only a patch removes it
- Build switch
- CONFIG_RT_MUTEXES
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-06-25 (4 months ago)source
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- 0.12%, higher than 1.8% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- kernel/locking
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 5.10.261 | 5.10.261 | bfbc047ceb42 |
| 5.15.212 | 5.15.212 | 4ffacf76a457 |
| 6.1.175 | 6.1.177 | 4afda3a1da02 |
| 6.6.140 | 6.6.144 | 6707d7e0b717 |
| 6.12.86 | 6.12.95 | 5799f9bd7fee |
| 6.18.27 | 6.18.36 | a388e3dfaf95 |
| 7.0.4 | 7.0.13 | 55363fa0a045 |
| 7.1 | 7.1 | 40a25d59e85b |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4700-1 | 2026-07-26 | bullseye 6.1.177-1~deb11u1 | tracker |
| DLA-4688-1 | 2026-07-18 | bookworm 6.1.177-1 | tracker |
| DSA-6381-1 | 2026-07-05 | trixie 6.12.95-1 | tracker |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2026-53163, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.