CVE-2026-23146: Linux kernel · Bluetooth: hci_uart: fix null-ptr-deref in hci_uart_write_work
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ccc683f597ceb28deb966427ae948e5ac739a909 : patch Linux kernel soon.
Data as of 26 Oct 2026, 16:53 UTC
Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-06-10.
- Patch
- Available – fixed in ccc683f597ceb28deb966427ae948e5ac739a909, b0a900939e7e4866d9b90e9112514b72c451e873, 937a573423ce5a96fdb1fd425dc6b8d8d4ab5779 +12
Exploitation evidence
Disclosed: evidence found.
CVE published 14 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in Linux kernel versions 6.15, 6.14, 6.12.69, 6.6.123, 6.1.162, and others as listed. Users and administrators should upgrade to these fixed versions to remediate the issue.
Description
A race condition in the Linux kernel Bluetooth hci_uart driver can cause a null pointer dereference in hci_uart_write_work. This occurs when a TTY write wakeup schedules work before the private data structure hu->priv is initialized, leading to a potential kernel crash.
References
- git.kernel.org/stable/c/b0a900939e7e4866d9b90e9112514b72c451e873 (opens in a new tab)
- git.kernel.org/stable/c/ccc683f597ceb28deb966427ae948e5ac739a909 (opens in a new tab)
- git.kernel.org/stable/c/937a573423ce5a96fdb1fd425dc6b8d8d4ab5779 (opens in a new tab)
- git.kernel.org/stable/c/186d147cf7689ba1f9b3ddb753ab634a84940cc9 (opens in a new tab)
- git.kernel.org/stable/c/53e54cb31e667fca05b1808b990eac0807d1dab0 (opens in a new tab)
- git.kernel.org/stable/c/03e8c90c62233382042b7bd0fa8b8900552fdb62 (opens in a new tab)
- git.kernel.org/stable/c/0c3cd7a0b862c37acbee6d9502107146cc944398 (opens in a new tab)