PatchSiren cyber security CVE debrief
CVE-2026-23146 Linux CVE debrief
A null pointer dereference vulnerability was found in the Linux kernel's Bluetooth hci_uart module. The vulnerability occurs when a TTY write wakeup happens during the window where hci_uart_set_proto() has set HCI_UART_PROTO_INIT but hci_uart_register_dev() has not yet called proto->open() to initialize hu->priv. This can lead to a null pointer dereference in hci_uart_write_work() when proto->dequeue() accesses hu->priv.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-02-14
- Original CVE updated
- 2026-10-19
- Advisory published
- 2026-02-14
- Advisory updated
- 2026-10-19
Who should care
Linux kernel maintainers, users, and administrators should assess exposure and prioritize verification of affected versions. Affected Linux kernel deployments require operator, platform, vulnerability-management, and security-team impact review. Linux distributions and package maintainers may need to provide updates. Security teams should monitor for potential exploitation attempts and verify affected versions.
Why it matters
A null pointer dereference vulnerability was found in the Linux kernel's Bluetooth hci_uart module. This vulnerability can lead to a denial of service or potentially allow an attacker to execute arbitrary code. Linux kernel maintainers and users should assess exposure and prioritize verification of affected versions.
- Verify affected versions and assess exposure
- Monitor for potential exploitation attempts
- Apply patches from Linux kernel maintainers
Technical summary
The vulnerability is caused by a race condition between hci_uart_set_proto() and hci_uart_register_dev(). 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.
Defensive priority
Linux kernel maintainers and users should assess exposure and prioritize verification of affected versions.
Recommended defensive actions
- Review and apply patches from Linux kernel maintainers
- Verify affected versions and assess exposure
- Monitor for potential exploitation attempts
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
Evidence notes
The CVE record and source item provide details about the vulnerability, including a description of the issue and references to affected versions. Linux kernel maintainers and users should verify affected versions, assess exposure, and prioritize verification. The vulnerability is caused by a race condition between hci_uart_set_proto() and hci_uart_register_dev(). Evidence is limited to CVE Program and supplemental references.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-23146 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-23146
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-23146 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-23146
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Bluetooth: hci_uart: fix null-ptr-deref in hci_uart_write_work
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/23xxx/CVE-2026-23146.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/b0a900939e7e4866d9b90e9112514b72c451e873
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/ccc683f597ceb28deb966427ae948e5ac739a909
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/937a573423ce5a96fdb1fd425dc6b8d8d4ab5779
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/186d147cf7689ba1f9b3ddb753ab634a84940cc9
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/53e54cb31e667fca05b1808b990eac0807d1dab0
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/03e8c90c62233382042b7bd0fa8b8900552fdb62
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/0c3cd7a0b862c37acbee6d9502107146cc944398
Supplemental source
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.