CVE-2026-23146 — Bluetooth: hci_uart: fix null-ptr-deref in hci_uart_write_work
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_uart: fix null-ptr-deref in hci_uart_write_work hci_uart_set_proto() sets HCI_UART_PROTO_INIT before calling hci_uart_register_dev(), which calls proto->open() to initialize hu->priv. However, if a TTY write wakeup occurs during this window, hci_uart_tx_wakeup() may schedule write_work before hu->priv is initialized, leading to a NULL pointer dereference in hci_uart_write_work() when proto->dequeue() accesses hu->priv. The race condition is: CPU0 CPU1 ---- ---- hci_uart_set_proto() set_bit(HCI_UART_PROTO_INIT) hci_uart_register_dev() tty write wakeup hci_uart_tty_wakeup() hci_uart_tx_wakeup() schedule_work(&hu->write_work) proto->open(hu) // initializes hu->priv hci_uart_write_work() hci_uart_dequeue() proto->dequeue(hu) // accesses hu->priv (NULL!) Fix this by moving set_bit(HCI_UART_PROTO_INIT) after proto->open() succeeds, ensuring hu->priv is initialized before any work can be scheduled.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.1% (30-day exploitation probability)+0
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 5.15.181 and < 5.15.199≥ 02e1bcdfdf769974e7e9fa285e295cd9852e2a38 and < 186d147cf7689ba1f9b3ddb753ab634a84940cc9≥ 281782d2c6730241e300d630bb9f200d831ede71 and < 53e54cb31e667fca05b1808b990eac0807d1dab0≥ 5df5dafc171b90d0b8d51547a82657cd5a1986c7 and < 03e8c90c62233382042b7bd0fa8b8900552fdb62≥ 5df5dafc171b90d0b8d51547a82657cd5a1986c7 and < 0c3cd7a0b862c37acbee6d9502107146cc944398version 1dcf08fcff5ca529de6dc0395091f28854f4e54aversion 8e5aff600539e5faea294d9612cca50220e602b8version db7509fa110dd9b11134b75894677f30353b2c51 and 11 more≥ 5.10.237 and < 5.10.249≥ 80f14e9de6a43a0bd8194cad1003a3e6dcbc3984 and < 937a573423ce5a96fdb1fd425dc6b8d8d4ab5779≥ 6.1.135 and < 6.1.162≥ 6.6.88 and < 6.6.123≥ 6.12.24 and < 6.12.69≥ 5.4.293 and < 5.5≥ 6.13.12 and < 6.14≥ 6.14.3 and < 6.15version 6.15≥ 9e5a0f5777162e503400c70c6ed25fbbe2d38799 and < ccc683f597ceb28deb966427ae948e5ac739a909≥ a40f94f7caa8d3421b64f63ac31bc0f24c890f39 and < b0a900939e7e4866d9b90e9112514b72c451e873 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel |
≥ 5.10.237 and < 5.10.249≥ 5.4.293 and < 5.5≥ 5.15.181 and < 5.15.199≥ 6.1.135 and < 6.1.162≥ 6.6.88 and < 6.6.123≥ 6.12.24 and < 6.12.69≥ 6.13.12 and < 6.14≥ 6.14.3 and < 6.18.9 and 7 moreversion 6.19-rc1version 6.19-rc2version 6.19-rc3version 6.19-rc4version 6.19-rc5version 6.19-rc6version 6.19-rc7 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.5 | CVSS 3.1 | Medium | 1.8 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.14%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 5.5
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
7 on the record
- git.kernel.org/stable/c/ccc683f597ceb28deb966427ae948e5ac739a909
- git.kernel.org/stable/c/937a573423ce5a96fdb1fd425dc6b8d8d4ab5779
- git.kernel.org/stable/c/b0a900939e7e4866d9b90e9112514b72c451e873
- git.kernel.org/stable/c/53e54cb31e667fca05b1808b990eac0807d1dab0
- git.kernel.org/stable/c/03e8c90c62233382042b7bd0fa8b8900552fdb62
- git.kernel.org/stable/c/0c3cd7a0b862c37acbee6d9502107146cc944398
- git.kernel.org/stable/c/186d147cf7689ba1f9b3ddb753ab634a84940cc9
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 10h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 10h
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-23146 is "Bluetooth: hci_uart: fix null-ptr-deref in hci_uart_write_work", rated Medium. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.14% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.