CVE-2026-98290·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup rfcomm_sock_cleanup_listen() closes unaccepted child sockets through rfcomm_sock_close(), which takes the child socket lock before rfcomm_dlc_close() acquires rfcomm_mutex. The RFCOMM worker takes these locks in reverse order while handling connections and DLC state changes, so lockdep reports a possible deadlock. Close dequeued children without taking their socket lock. The accept queue owns a reference to each child, and bt_accept_dequeue() locks the child while unlinking it and clearing its parent pointer. Dropping the child lock makes it important to prevent a concurrent rfcomm_connect_ind() from enqueueing a new child after cleanup observes an empty queue. Set a listening socket to BT_CLOSED while its lock is still held, before dropping the lock and draining the queue. The state check in rfcomm_connect_ind() then rejects new children once cleanup starts.
- Severity
- high
- Software
- Kernel
- Fixed in
- 5.15.222, 6.1.189, 6.6.158, 6.12.112, 6.18.54, 7.2.8, 7.3
- 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.24% — higher than 15% 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-98290 scores 7.5 on CVSS, so a successful attack would be serious — but at 0.24%, 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.
How to fix this CVE
Update your Linux kernel to a patched stable release to resolve a socket lock inversion vulnerability in the Bluetooth RFCOMM subsystem. Users should upgrade to kernel 5.15.222, 6.1.189, 6.6.158, 6.12.112, 6.18.54, or 7.2.8 depending on their current kernel branch, or install the patched kernel package provided by their Linux distribution. This prevents potential deadlock conditions during Bluetooth connection handling.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your current kernel version with `uname -r` and compare against the fixed versions (5.15.222, 6.1.189, 6.6.158, 6.12.112, 6.18.54, 7.2.8)
- Step 2: Verify Bluetooth RFCOMM is in use by checking `lsmod | grep rfcomm` and `systemctl status bluetooth`
- Step 3: Search kernel logs for lock-related warnings with `sudo dmesg | grep -i 'lock\|deadlock\|rfcomm'` or `sudo journalctl -k | grep -i 'lock\|deadlock\|rfcomm'`
- Step 4: After patching, reboot and confirm the new kernel version with `uname -r`, then re-run Step 3 to confirm no warnings appear
FAQ
What is CVE-2026-98290?
This vulnerability is a socket lock inversion issue in the Linux kernel's Bluetooth RFCOMM (Radio Frequency Communication) module that can cause deadlocks when cleaning up unaccepted child sockets on listener teardown. The RFCOMM worker acquires locks in reverse order compared to listener cleanup, creating a potential deadlock scenario.
Is CVE-2026-98290 being actively exploited?
No, this CVE is not listed as actively exploited by CISA and no public exploits are available. However, it should still be patched promptly as it can cause denial of service through system deadlock.
What versions of Kernel are affected by CVE-2026-98290?
All Linux kernel versions prior to the stable branch fixes are affected. Specifically, patches are available for 5.15.222+, 6.1.189+, 6.6.158+, 6.12.112+, 6.18.54+, and 7.2.8+. Users should upgrade within their current stable branch rather than jumping to mainline.
How do I check if my server is vulnerable to CVE-2026-98290?
Run `uname -r` to get your kernel version, then compare it against the fixed versions. If your version is older than the patched release for your branch (e.g., 6.1.188 or earlier for the 6.1 branch), your system is vulnerable.
Does Defensia detect CVE-2026-98290?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2026-98290 will appear in your dashboard with remediation steps and upgrade recommendations.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/18174b166547ef41973cc19feb5ef9cab39a8def
- https://git.kernel.org/stable/c/4aafb47301a799d3e01230d6568c4e93524e1523
- https://git.kernel.org/stable/c/801fb950cae7048eb7d83b18857d1ca37b8cd5a4
- https://git.kernel.org/stable/c/bfce253f039eb5f58b810af267942a9f59207254
- https://git.kernel.org/stable/c/c6792c441767256030606eb82dca5d5fc360dd9a
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-98290. Free for 1 server.
Get started free