Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-43119: Bluetooth: hci_sync: annotate data-races around hdev->req_status

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.11% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 4.20, 40734ce8efc34c4a0d0222855798c0dc14b65f2e, 5.1; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.

Low priority for now. Upgrade to Linux Linux 4.20, 40734ce8efc34c4a0d0222855798c0dc14b65f2e, 5.1; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 6, 2026
Updated
Nov 6, 2026
EPSS
0.1% · 1th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-43119

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.2 and later · before 6.12.83
  • linux linux kernel6.13 and later · before 6.18.24
  • linux linux kernel6.19 and later · before 6.19.14
  • linux linux kernel7.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 8603d49906b231bbcd9141db7d096fa1041bc379, 0e061885bfcd65ef5d09f154f3c3c3491cc7544a, a3d50fb7ce931f08a2c6194fdc4c9a56c9ed4153, 5.2affected
    • f80c5dad7b6467b884c445ffea45985793b4b2d0 and later · before ff5855e8891e1e2490741366d087fd2fbcaabc4aaffected · git
    • f80c5dad7b6467b884c445ffea45985793b4b2d0 and later · before e51042ddc0b20d9bda5eb6dcf85a2668f9c5dae4affected · git
    • f80c5dad7b6467b884c445ffea45985793b4b2d0 and later · before 6e539907c0d11f514c5e0b049b27b04dff48a5b1affected · git
    • f80c5dad7b6467b884c445ffea45985793b4b2d0 and later · before a7a1cdb4a64ca74eb95cc46648fccb8cd3f9af27affected · git
    • f80c5dad7b6467b884c445ffea45985793b4b2d0 and later · before 40734ce8efc34c4a0d0222855798c0dc14b65f2eaffected · git
    • f80c5dad7b6467b884c445ffea45985793b4b2d0 and later · before b6807cfc195ef99e1ac37b2e1e60df40295daa8caffected · git
    • 4.19.47 and later · before 4.20affected · semver
    • 5.0.20 and later · before 5.1affected · semver
    • 5.1.6 and later · before 5.2affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:13linuxbefore 6.12.85-16.12.85-1
Debian:14linuxbefore 6.19.14-16.19.14-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-43117May 6, 2026 · btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file()
    36Monitor
  • ← EarlierCVE-2026-43118May 6, 2026 · btrfs: fix zero size inode with non-zero size after log replay
    22Monitor
  • Later →CVE-2026-43120May 6, 2026 · RDMA/irdma: Fix double free related to rereg_user_mr
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux4.20Vendor (CNA)
Linux Linux40734ce8efc34c4a0d0222855798c0dc14b65f2eVendor (CNA)
Linux Linux5.1Vendor (CNA)
Linux Linux5.2Vendor (CNA)
Linux Linux6e539907c0d11f514c5e0b049b27b04dff48a5b1Vendor (CNA)
Linux Linuxa7a1cdb4a64ca74eb95cc46648fccb8cd3f9af27Vendor (CNA)
Linux Linuxb6807cfc195ef99e1ac37b2e1e60df40295daa8cVendor (CNA)
Linux Linuxe51042ddc0b20d9bda5eb6dcf85a2668f9c5dae4Vendor (CNA)
Linux Linuxff5855e8891e1e2490741366d087fd2fbcaabc4aVendor (CNA)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
debian:linux6.12.85-1 · Debian:13Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records