CVE-2026-43119General(linux / linux_kernel)

LOWCVSS 5.5 · MEDIUM

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch linux linux_kernel systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD 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).

0.5/ 10 priority

Sources & remediation

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • linux_kernel

Threat summary

  • Patch or workaround signal is available
  • 2 mentions across 2 observed days
  • Momentum state: stable

What's happening

  • Patch or workaround mentioned in 1 signal
  • Technical details provided in 2 signals
  • General: 1 classified signal
  • Disclosure: 1 classified signal
  • Peaked 1d ago at 1 mentions (2026-05-06); latest day: 1
  • 2 total mentions across 2 days

Affected systems

Vendors
Products
linux_kernel

1 version affected across 1 product

Deep dive

Activity timeline2 mentions / 2d
00111Mentions · 2026-05-06: 1Mentions · 2026-05-07: 1Patch / Workaround · 2026-05-07: 1Technical Details · 2026-05-06: 1Technical Details · 2026-05-07: 105-0605-07
Signal classification2 categories
General
150.0%
Disclosure
150.0%
Referenced assets2 URLs
Classification over time
DateTotalLabels
2026-05-061
General1
2026-05-071
Disclosure1
Full discourse2 posts
  • WindowsForum@windowsforum
    Disclosure

    🪟 CVE-2026-43119 is the kind of bug security folks love: not loud RCE—just a Bluetooth race condition fixed with READ_ONCE/WRITE_ONCE. Still matters: undefined behavior loves chaos. #Windows #Security https://windowsforum.com/threads/cve-2026-43119-linux-bluetooth-hci_sync-race-fixed-with-read_once-write_once.416780/?utm_source=x&utm_medium=social&utm_campaign=news_node84 #LinuxKernel #BluetoothSecurity #Cve2026 https://t.co/kmzDXqilaZ

    Post summary

    The post announces CVE‑2026‑43119, a Bluetooth race condition in Windows, and notes the issue has been fixed with READ_ONCE/WRITE_ONCE.

    0000055
    1.1K followersView on X
  • Vulmon Vulnerability Feed@VulmonFeeds
    General

    CVE-2026-43119 Data Race Annotation in Linux Kernel Bluetooth hci_sync hdev->req_status https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-43119

    Post summary

    The post lists CVE‑2026‑43119 as a data race bug in the Linux kernel’s Bluetooth implementation, providing a brief description and a link to a Vulmon page for more details, but offers no actionable or exploit information.

    0000065
    4.0K followersView on X
CPE platform detail6 entries

6 of 6 entries

PartVendorProductVersionTarget SWTarget HW
OSlinuxlinux_kernel---
OSlinuxlinux_kernel7.0--
OSlinuxlinux_kernel7.0--
OSlinuxlinux_kernel7.0--
OSlinuxlinux_kernel7.0--
OSlinuxlinux_kernel7.0--

Explore more