# Bluetooth: L2CAP: reject BR/EDR signaling packets over MTUsig

CVE record · `CVE-2026-53208`

- **Identifiers:** `CVE-2026-53208`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 25 Jun 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 25 Jun 2026, 08:39 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: `1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before e05c4ac575b457978a7ef441053394169084869c` (git)
  - affected: `1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before fa5823126239b3e453fac1a2fe50726c7f4a55e1` (git)
  - affected: `1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before b20e8a98dd29b121f58fcdf51e8576119aba536a` (git)
  - affected: `1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before 214a2042b16b3c8d798a8b9ef9f36094f13a9859` (git)
  - affected: `1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before a8335f3db15bd1e0e82e0db5d488fabc7d10d1ab` (git)
  - affected: `1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before dedc92b96dc1d8919a3bdf2495ede68922ef7ebc` (git)
  - affected: `1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before e2b8acf9405bd9b1baf1c54dc897b0905db689bf` (git)
  - affected: `1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before dd214733544427587a95f66dbf3adff072568990` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `2.6.12`
  - unaffected: `before 2.6.12` (semver)
  - unaffected: `5.10.259 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.210 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.176 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.143 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.94 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.36 to 6.18.*, inclusive` (semver)
  - unaffected: `7.0.13 to 7.0.*, inclusive` (semver)
  - unaffected: `7.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Linux kernel versions with the Bluetooth L2CAP signaling code are affected, from the initial git import until the fixes listed in the source (for example commit e05c4ac575b457978a7ef441053394169084869c and others), and 2.6.12 is listed as affected. A Bluetooth BR/EDR peer within radio range, before pairing, can send one oversized signaling packet containing many commands, forcing the target to send many responses. Upgrade to a fixed stable kernel release, such as 5.10.259 or later in the 5.10 series, 5.15.210 or later, 6.1.176 or later, or 6.6.143 or later. No workaround is given.

Written 17 Nov 2026.

## 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

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0013, the 2nd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 25 Jun 2026, 08:39 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-53208)
- 25 Jun 2026, 09:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-53208)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/e05c4ac575b457978a7ef441053394169084869c>
- <https://git.kernel.org/stable/c/fa5823126239b3e453fac1a2fe50726c7f4a55e1>
- <https://git.kernel.org/stable/c/b20e8a98dd29b121f58fcdf51e8576119aba536a>
- <https://git.kernel.org/stable/c/214a2042b16b3c8d798a8b9ef9f36094f13a9859>
- <https://git.kernel.org/stable/c/a8335f3db15bd1e0e82e0db5d488fabc7d10d1ab>
- <https://git.kernel.org/stable/c/dedc92b96dc1d8919a3bdf2495ede68922ef7ebc>
- <https://git.kernel.org/stable/c/e2b8acf9405bd9b1baf1c54dc897b0905db689bf>
- <https://git.kernel.org/stable/c/dd214733544427587a95f66dbf3adff072568990>

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

---

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