CVE-2026-43119: Bluetooth: hci_sync: annotate data-races around hdev->req_status
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hcisync: annotate data-races around hdev->reqstatus
hcicmdsyncsk() sets hdev->reqstatus under hdev->reqlock:
hdev->reqstatus = HCIREQPEND;
However, several other functions read or write hdev->reqstatus without holding any lock:
- hcisendcmdsync() reads reqstatus in hcicmdwork (workqueue) - hcicmdsynccomplete() reads/writes from HCI event completion - hcicmdsynccancel() / hcicmdsynccancelsync() read/write - hciabortconn() reads in connection abort path
Since hcicmdsyncsk() runs on hdev->reqworkqueue while hcisendcmdsync() runs on hdev->workqueue, these are different workqueues that can execute concurrently on different CPUs. The plain C accesses constitute a data race.
Add READONCE()/WRITEONCE() annotations on all concurrent accesses to hdev->reqstatus to prevent potential compiler optimizations that could affect correctness (e.g., load fusing in the waitevent condition or store reordering).
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-43119?
CVE-2026-43119 has been classified with a medium severity level due to potential data races in Bluetooth functionality.
How do I fix CVE-2026-43119?
To fix CVE-2026-43119, update your Linux kernel to the latest stable version where the vulnerability has been patched.
What systems are affected by CVE-2026-43119?
CVE-2026-43119 affects the Linux kernel, particularly versions with Bluetooth functionality that utilize the hdev->req_status variable.
What impact does CVE-2026-43119 have on the system?
CVE-2026-43119 may lead to unpredictable behavior or crashes in systems utilizing Bluetooth due to potential data races.
Is there a workaround for CVE-2026-43119?
As a workaround for CVE-2026-43119, users can disable Bluetooth functionality until the system can be updated.