CVE-2026-43334: Bluetooth: SMP: force responder MITM requirements before building the pairing response
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: SMP: force responder MITM requirements before building the pairing response
smp_cmd_pairing_req() currently builds the pairing response from the
initiator auth_req before enforcing the local BT_SECURITY_HIGH
requirement. If the initiator omits SMP_AUTH_MITM, the response can
also omit it even though the local side still requires MITM.
tk_request() then sees an auth value without SMP_AUTH_MITM and may
select JUST_CFM, making method selection inconsistent with the pairing
policy the responder already enforces.
When the local side requires HIGH security, first verify that MITM can
be achieved from the IO capabilities and then force SMP_AUTH_MITM in the
response in both rsp.auth_req and auth. This keeps the responder auth bits
and later method selection aligned.
Security readout for executives and security teams
Plain-English summary
CVE-2026-43334 is a Linux kernel Bluetooth pairing flaw. A nearby attacker could potentially influence pairing so a device requiring man-in-the-middle protection responds without consistently enforcing it. This matters most for Linux systems with Bluetooth enabled and security-sensitive pairing workflows. The CVSS score is high, but sources do not show active exploitation.
Executive priority
Treat as a high-priority kernel update for Bluetooth-enabled Linux fleets. Business urgency is highest for mobile, embedded, or customer-facing devices that pair with peripherals. It is not currently evidenced as internet-exploitable or actively exploited.
Technical view
The issue is in Linux Bluetooth SMP pairing response handling. smp_cmd_pairing_req() built the response from the initiator auth_req before enforcing local BT_SECURITY_HIGH MITM requirements. If MITM was omitted by the initiator, later tk_request() method selection could choose JUST_CFM, misaligning responder policy and authentication bits.
Likely exposure
Exposure is limited to adjacent Bluetooth range. Relevant assets are Linux systems with Bluetooth enabled, especially those accepting pairing while configured to require HIGH security. Systems without Bluetooth hardware, disabled Bluetooth, or no pairing role exposure are less likely affected.
Exploitation context
The CVSS vector is adjacent-network, low complexity, no privileges, and no user interaction. The provided sources do not state public exploit availability or active exploitation, and KEV status is false.
Researcher notes
The vulnerable behavior concerns responder-side SMP auth_req construction before enforcing BT_SECURITY_HIGH. The fix forces SMP_AUTH_MITM when local HIGH security requires it and checks IO capability feasibility first. Affected version data in the source bundle is limited and should be reconciled with distro backports.
Mitigation direction
Apply Linux stable kernel updates containing the referenced Bluetooth SMP fix.
Prioritize Bluetooth-enabled laptops, embedded devices, kiosks, and IoT gateways.
If patch timing is uncertain, check distribution or device vendor guidance.
Disable Bluetooth where it is not required for business operations.
Restrict pairing availability on sensitive systems until patched.
Validation and detection
Inventory Linux kernel versions across Bluetooth-capable assets.
Identify systems with Bluetooth enabled and discoverable or pairable workflows.
Check vendor advisories for backported fixes matching your distribution kernel.
Confirm the fix is present through vendor package metadata or kernel changelog.
Verify Bluetooth remains disabled on systems where it is not needed.
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-43334 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
9Source 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.