# Bluetooth: SMP: derive legacy responder STK authentication from MITM state

CVE record · `CVE-2026-31773`

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

Published by the CVE Program (CNA: Linux) at 1 May 2026, 14:15 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: `fff3490f47810e2d34b91fb9e31103e923b11c2f to before 9a38659a3d06080715691bd3139f9c4b61f688e3` (git)
  - affected: `fff3490f47810e2d34b91fb9e31103e923b11c2f to before 667f44f1392df6482483756458c48670e579e9ff` (git)
  - affected: `fff3490f47810e2d34b91fb9e31103e923b11c2f to before 929db734d12db41ca5f95424db4612397f1bd4a7` (git)
  - affected: `fff3490f47810e2d34b91fb9e31103e923b11c2f to before b1c6a8e554a39b222c0879a288ea98e338fc4d77` (git)
  - affected: `fff3490f47810e2d34b91fb9e31103e923b11c2f to before 0afc846bd80073ffcd2b8040f2b2fafaea3d9f72` (git)
  - affected: `fff3490f47810e2d34b91fb9e31103e923b11c2f to before 061ee71ac6b03c9f8432fe49538c3682bfcf4cf3` (git)
  - affected: `fff3490f47810e2d34b91fb9e31103e923b11c2f to before 9a6d0db176f082685e0b6149700c0baf3ce2aa8b` (git)
  - affected: `fff3490f47810e2d34b91fb9e31103e923b11c2f to before 20756fec2f0108cb88e815941f1ffff88dc286fe` (git)
  - affected: `14ec593d6bb050cf40a4ade2f9ac9ca050e0412c` (git)
  - affected: `3.15.5 to before 3.16` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `3.16`
  - unaffected: `before 3.16` (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

- 1 May 2026, 15:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-31773)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/9a38659a3d06080715691bd3139f9c4b61f688e3>
- <https://git.kernel.org/stable/c/667f44f1392df6482483756458c48670e579e9ff>
- <https://git.kernel.org/stable/c/929db734d12db41ca5f95424db4612397f1bd4a7>
- <https://git.kernel.org/stable/c/b1c6a8e554a39b222c0879a288ea98e338fc4d77>
- <https://git.kernel.org/stable/c/0afc846bd80073ffcd2b8040f2b2fafaea3d9f72>
- <https://git.kernel.org/stable/c/061ee71ac6b03c9f8432fe49538c3682bfcf4cf3>
- <https://git.kernel.org/stable/c/9a6d0db176f082685e0b6149700c0baf3ce2aa8b>
- <https://git.kernel.org/stable/c/20756fec2f0108cb88e815941f1ffff88dc286fe>

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-31773>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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