CVE-2026-53256·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: hold listener socket in rfcomm_connect_ind() rfcomm_get_sock_by_channel() scans rfcomm_sk_list under the list lock, but returns the selected listener after dropping that lock without taking a reference. rfcomm_connect_ind() then locks the listener, queues a child socket on it, and may notify it after unlocking it. The buggy scenario involves two paths, with each column showing the order within that path: rfcomm_connect_ind(): listener close: 1. Find parent in 1. close() enters rfcomm_get_sock_by_channel() rfcomm_sock_release(). 2. Drop rfcomm_sk_list.lock 2. rfcomm_sock_shutdown() without pinning parent. closes the listener. 3. Call lock_sock(parent) and 3. rfcomm_sock_kill() bt_accept_enqueue(parent, unlinks and puts parent. sk, true). 4. Read parent flags and may 4. parent can be freed. call sk_state_change(). If close wins the race, parent can be freed before rfcomm_connect_ind() reaches lock_sock(), bt_accept_enqueue(), or the deferred-setup callback. Take a reference on the listener before leaving rfcomm_sk_list.lock. After lock_sock() succeeds, recheck that it is still in BT_LISTEN before queueing a child, cache the deferred-setup bit while the parent is locked, and drop the reference after the last parent use. KASAN reported a slab-use-after-free in lock_sock_nested() from rfcomm_connect_ind(), with the freeing stack going through rfcomm_sock_kill() and rfcomm_sock_release().
- Severity
- high
- Software
- Kernel
- Fixed in
- 7.0.13
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.26% — higher than 18% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-53256 scores 8 on CVSS, so a successful attack would be serious — but at 0.26%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.19
Until: 7.0.13
Fixed in: 7.0.13
How to fix this CVE
Update your Linux kernel to version 7.0.13 or later to patch a critical Bluetooth RFCOMM race condition that can lead to use-after-free memory errors. This vulnerability affects the listener socket handling in rfcomm_connect_ind(), where improper reference counting allows concurrent socket operations to access freed memory. Apply the kernel update through your distribution's package manager and reboot to activate the patched kernel.
sudo dnf update kernel kernel-devel && sudo rebootDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your current kernel version with `uname -r` and compare against the affected range (6.19 to 7.0.13)
- Step 2: Verify if Bluetooth RFCOMM is loaded with `lsmod | grep rfcomm` — if output appears, the vulnerable component is present
- Step 3: Search kernel logs for use-after-free errors related to rfcomm: `dmesg | grep -i "use-after-free\|slab-use-after-free\|rfcomm" | tail -20`
- Step 4: After patching, confirm the new kernel is running with `uname -r` and verify it matches version 7.0.13 or later
FAQ
What is CVE-2026-53256?
This vulnerability is a race condition in the Linux kernel's Bluetooth RFCOMM subsystem where the listener socket lacks proper reference counting during concurrent connection and close operations. An attacker or race condition can cause the kernel to access memory that has already been freed, leading to potential system crash or privilege escalation.
Is CVE-2026-53256 being actively exploited?
No, CVE-2026-53256 is not listed on CISA's Known Exploited Vulnerabilities catalog and no public exploits are currently available. However, the vulnerability requires local access and low privileges to trigger.
What versions of Kernel are affected by CVE-2026-53256?
Linux kernel versions 6.19 through 7.0.12 are vulnerable. Version 7.0.13 and later contain the fix.
How do I check if my server is vulnerable to CVE-2026-53256?
Run `uname -r` to check your kernel version. If it reports a version between 6.19 and 7.0.12 inclusive, your system is vulnerable. Additionally, run `lsmod | grep rfcomm` to confirm if the Bluetooth RFCOMM module is loaded.
Does Defensia detect CVE-2026-53256?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2026-53256 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/1f73f92f66251065a5f39b09a47cf05ea14d3107
- https://git.kernel.org/stable/c/43c441edacf953b39517a44f5e5e10a93618b226
- https://git.kernel.org/stable/c/6f4462d12133106460d7c046b95aad2491e3fddf
- https://git.kernel.org/stable/c/8802413ce63175fb522a2bd609fb043a3550c720
- https://git.kernel.org/stable/c/a07d741c077d4e34b16458241a94d29039386553
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-53256. Free for 1 server.
Get started free