# Bluetooth: SMP: force responder MITM requirements before building the pairing response

CVE record · `CVE-2026-43334`

- **Identifiers:** `CVE-2026-43334`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 8 May 2026
- **Updated:** 19 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 8 May 2026, 13:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `2b64d153a0cc9d2b60e47be013cde8490f16e0a5 to before 425a22c5373d4e1b46492ab869074ebeeade61f3` (git)
  - affected: `2b64d153a0cc9d2b60e47be013cde8490f16e0a5 to before 7ab69426e7ecbd18a222ee2ec87ca612d30197d7` (git)
  - affected: `2b64d153a0cc9d2b60e47be013cde8490f16e0a5 to before 01bb4045d2306c266178f49ce0c3576d237a3040` (git)
  - affected: `2b64d153a0cc9d2b60e47be013cde8490f16e0a5 to before 91649c02c1baaa18cedf7fb425fa1f0f852c8183` (git)
  - affected: `2b64d153a0cc9d2b60e47be013cde8490f16e0a5 to before c8ff0ca6508535bccabd81c5c9dcc63de8a3d4fb` (git)
  - affected: `2b64d153a0cc9d2b60e47be013cde8490f16e0a5 to before fa14e0e19820b1bbdb42185c9c4efa950bcffef9` (git)
  - affected: `2b64d153a0cc9d2b60e47be013cde8490f16e0a5 to before ec17efb1ef91506cfd17a77692eaf4bbacb520ea` (git)
  - affected: `2b64d153a0cc9d2b60e47be013cde8490f16e0a5 to before d05111bfe37bfd8bd4d2dfe6675d6bdeef43f7c7` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `3.3`
  - unaffected: `before 3.3` (semver)
  - unaffected: `5.10.253 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.203 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.168 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.134 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.81 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.22 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19.12 to 6.19.*, inclusive` (semver)
  - unaffected: `7.0 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 8.8 High, CVSS 3.1: `CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from CNA (Linux)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0028, the 20th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 8 May 2026, 14:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-43334)

## Sources

- [CVE List: CVE-2026-43334](https://www.cve.org/CVERecord?id=CVE-2026-43334)
- [NVD: CVE-2026-43334](https://nvd.nist.gov/vuln/detail/CVE-2026-43334)

### References from the CNA

- <https://git.kernel.org/stable/c/425a22c5373d4e1b46492ab869074ebeeade61f3>
- <https://git.kernel.org/stable/c/7ab69426e7ecbd18a222ee2ec87ca612d30197d7>
- <https://git.kernel.org/stable/c/01bb4045d2306c266178f49ce0c3576d237a3040>
- <https://git.kernel.org/stable/c/91649c02c1baaa18cedf7fb425fa1f0f852c8183>
- <https://git.kernel.org/stable/c/c8ff0ca6508535bccabd81c5c9dcc63de8a3d4fb>
- <https://git.kernel.org/stable/c/fa14e0e19820b1bbdb42185c9c4efa950bcffef9>
- <https://git.kernel.org/stable/c/ec17efb1ef91506cfd17a77692eaf4bbacb520ea>
- <https://git.kernel.org/stable/c/d05111bfe37bfd8bd4d2dfe6675d6bdeef43f7c7>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-43334>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-43334/>. Everything for agents: <https://agentprime.io/llms.txt>.
