CVE-2026-98456·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: mgmt: fix race in read_unconf_index_list() read_unconf_index_list() counts unconfigured controllers before allocating its response, then checks the device flags again while filling it. hci_dev_list_lock stabilizes list membership, but it does not serialize the per-device flags. During asynchronous controller setup, the worker can set HCI_UNCONFIGURED and clear HCI_SETUP between the two passes. A controller omitted from the allocation count can then become eligible for the fill pass, causing an out-of-bounds write to rp->index[]. Allocate space for every device on hci_dev_list. Since list membership cannot change while hci_dev_list_lock is held, the response remains large enough regardless of flag transitions. The reported count and response length still include only eligible unconfigured controllers.
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.6.158, 6.12.112, 6.18.55, 7.2.9, 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.17% — higher than 6% 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-98456 scores 7 on CVSS, so a successful attack would be serious — but at 0.17%, 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 branch version to fix a race condition in Bluetooth management that can cause memory corruption. If you're running kernel 6.6.x, update to 6.6.158 or later; for 6.12.x use 6.12.112+; for 6.18.x use 6.18.55+; for 7.2.x use 7.2.9+. Alternatively, install your distribution's patched kernel package rather than jumping to mainline.
sudo dnf upgrade 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 fixed versions (6.6.158, 6.12.112, 6.18.55, 7.2.9 or later depending on your branch)
- Step 2: Verify if Bluetooth subsystem is loaded with `lsmod | grep -i bluetooth` — this vulnerability affects the HCI device management layer
- Step 3: Search dmesg and system logs for out-of-bounds memory access warnings or kernel panics related to Bluetooth management with `sudo journalctl -xe | grep -i 'bluetooth\|mgmt\|unconfigured'`
- Step 4: After applying the patch, confirm the new kernel version is running with `uname -r` and reboot if needed with `sudo reboot`
FAQ
What is CVE-2026-98456?
This is a race condition in the Linux kernel's Bluetooth management code where asynchronous controller setup can cause a mismatch between the allocated response buffer size and the actual number of unconfigured devices, resulting in out-of-bounds memory writes.
Is CVE-2026-98456 being actively exploited?
No, this vulnerability is not listed on the CISA Known Exploited Vulnerabilities catalog and no public exploits are available. However, it is a local privilege escalation vulnerability that requires prior system access.
What versions of Kernel are affected by CVE-2026-98456?
The vulnerability affects multiple stable branches prior to the following fixed versions: 6.6.158, 6.12.112, 6.18.55, 7.2.9, and mainline 7.3. Systems running older versions of these branches are vulnerable.
How do I check if my server is vulnerable to CVE-2026-98456?
Run `uname -r` to get your kernel version. If it matches a branch (e.g., 6.6.x) and the patch number is below the fixed version (e.g., 6.6.158), your system is vulnerable. Cross-reference your exact version against the fixed releases provided.
Does Defensia detect CVE-2026-98456?
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-98456 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/2e8bba0360d1379bfa8da47c8f5dadbb10a3fba1
- https://git.kernel.org/stable/c/416546cd6a54e9b68f2b91bc680b1ee17dcd77a1
- https://git.kernel.org/stable/c/524e0450dd9a396f99a81b045219b0e2ea0dab57
- https://git.kernel.org/stable/c/76dc7e0297f6f7ebefc36a69251e3f4a676d9853
- https://git.kernel.org/stable/c/8ddf962c76432a10a6cb80042875cbc48a9c056b
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-98456. Free for 1 server.
Get started free