CVE-2026-43019: Bluetooth: hci_conn: fix potential UAF in set_cig_params_sync
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_conn: fix potential UAF in set_cig_params_sync
hci_conn lookup and field access must be covered by hdev lock in
set_cig_params_sync, otherwise it's possible it is freed concurrently.
Take hdev lock to prevent hci_conn from being deleted or modified
concurrently. Just RCU lock is not suitable here, as we also want to
avoid "tearing" in the configuration.
Security readout for executives and security teams
Plain-English summary
A race condition in the Linux Bluetooth subsystem can leave the kernel using a connection object after another operation frees it. A successful local attack could potentially compromise confidentiality, integrity, and availability. Exact exposure depends on the installed kernel and distributor backports.
Executive priority
Treat as a high-priority kernel update, especially for shared endpoints or systems allowing untrusted local access. It is not evidence of an internet-exploitable emergency or known active exploitation. Use an accelerated, tested patch cycle based on distributor confirmation.
Technical view
set_cig_params_sync can look up and access an hci_conn without holding the hdev lock, allowing concurrent deletion or modification and a potential use-after-free. The documented correction protects the lookup and field access with the hdev lock. RCU alone is insufficient because configuration tearing must also be prevented.
Likely exposure
Prioritize Linux systems with Bluetooth enabled or used and kernels identified as affected, including listed 6.6 through 7.0 branches. The supplied version data is irregular, so version numbers alone may misclassify distributor kernels containing backported fixes. Confirm patch status with the kernel supplier.
Exploitation context
The CVSS 3.1 assessment is 7.8: local access, low complexity, low privileges, and no user interaction, with potentially high confidentiality, integrity, and availability impact. The bundle does not establish active exploitation, and the CVE is not listed as KEV.
Researcher notes
The core issue is an hci_conn lifetime and consistency race in set_cig_params_sync. Concurrent deletion or modification can produce a use-after-free or torn configuration. The supplied record provides stable-kernel correction commits but no public exploit evidence, reproduction details, CWE assignment, or proof that every listed branch is uniformly affected.
Mitigation direction
Install a vendor-supported kernel containing the applicable referenced Linux stable fix.
Check distributor guidance because kernel version strings may not reveal backported fixes.
Prioritize multi-user systems where untrusted local users can access Bluetooth functionality.
Apply normal change controls and test Bluetooth-dependent workloads before broad rollout.
Validation and detection
Inventory installed kernel builds and identify systems using Bluetooth functionality.
Confirm the applicable fix commit or distributor backport is present in each kernel build.
Verify set_cig_params_sync protects hci_conn lookup and access with the hdev lock.
After updating, confirm systems boot normally and required Bluetooth workflows still operate.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-43019 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
6Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.