CVE-2026-43119Bluetooth: hci_sync: annotate data-races around hdev->req_status
- 5.5MediumCVSS base score
- 0.11%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: annotate data-races around hdev->req_status __hci_cmd_sync_sk() sets hdev->req_status under hdev->req_lock: hdev->req_status = HCI_REQ_PEND; However, several other functions read or write hdev->req_status without holding any lock: - hci_send_cmd_sync() reads req_status in hci_cmd_work (workqueue) - hci_cmd_sync_complete() reads/writes from HCI event completion - hci_cmd_sync_cancel() / hci_cmd_sync_cancel_sync() read/write - hci_abort_conn() reads in connection abort path Since __hci_cmd_sync_sk() runs on hdev->req_workqueue while hci_send_cmd_sync() runs on hdev->workqueue, these are different workqueues that can execute concurrently on different CPUs. The plain C accesses constitute a data race. Add READ_ONCE()/WRITE_ONCE() annotations on all concurrent accesses to hdev->req_status to prevent potential compiler optimizations that could affect correctness (e.g., load fusing in the wait_event condition or store reordering).
Timeline
ID reserved
By Linux
- 5 days later
· 5 days later
Published
- 6 months later
· 6 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.11% · top 98% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected f80c5dad7b6467b884c445ffea45985793b4b2d0 – < ff5855e8891e1e2490741366d087fd2fbcaabc4a
- affected f80c5dad7b6467b884c445ffea45985793b4b2d0 – < e51042ddc0b20d9bda5eb6dcf85a2668f9c5dae4
- affected f80c5dad7b6467b884c445ffea45985793b4b2d0 – < 6e539907c0d11f514c5e0b049b27b04dff48a5b1
- affected f80c5dad7b6467b884c445ffea45985793b4b2d0 – < a7a1cdb4a64ca74eb95cc46648fccb8cd3f9af27
- affected f80c5dad7b6467b884c445ffea45985793b4b2d0 – < 40734ce8efc34c4a0d0222855798c0dc14b65f2e
- affected f80c5dad7b6467b884c445ffea45985793b4b2d0 – < b6807cfc195ef99e1ac37b2e1e60df40295daa8c
- affected 8603d49906b231bbcd9141db7d096fa1041bc379
- affected 0e061885bfcd65ef5d09f154f3c3c3491cc7544a
- affected a3d50fb7ce931f08a2c6194fdc4c9a56c9ed4153
- affected 4.19.47 – < 4.20
- affected 5.0.20 – < 5.1
- affected 5.1.6 – < 5.2
- affected 5.2
- unaffected < 5.2
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.83 – ≤ 6.12.*
- unaffected 6.18.24 – ≤ 6.18.*
- unaffected 6.19.14 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References6
- https://git.kernel.org/stable/c/ff5855e8891e1e2490741366d087fd2fbcaabc4a (opens in a new tab)
- https://git.kernel.org/stable/c/e51042ddc0b20d9bda5eb6dcf85a2668f9c5dae4 (opens in a new tab)
- https://git.kernel.org/stable/c/6e539907c0d11f514c5e0b049b27b04dff48a5b1 (opens in a new tab)
- https://git.kernel.org/stable/c/a7a1cdb4a64ca74eb95cc46648fccb8cd3f9af27 (opens in a new tab)
- https://git.kernel.org/stable/c/40734ce8efc34c4a0d0222855798c0dc14b65f2e (opens in a new tab)
- https://git.kernel.org/stable/c/b6807cfc195ef99e1ac37b2e1e60df40295daa8c (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-27647 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-43119)Record last updated .