# Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop

CVE record · `CVE-2026-31498`

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

Published by the CVE Program (CNA: Linux) at 22 Apr 2026, 13:54 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: `96298f640104e4cd9a913a6e50b0b981829b94ff to before 9760b83cfd24b38caee663f429011a0dd6064fa9` (git)
  - affected: `96298f640104e4cd9a913a6e50b0b981829b94ff to before de37e2655b7abc3f59254c6b72256840f39fc6d5` (git)
  - affected: `96298f640104e4cd9a913a6e50b0b981829b94ff to before e7aab23b7df89a3d754a5f0a7d2237548b328bd0` (git)
  - affected: `96298f640104e4cd9a913a6e50b0b981829b94ff to before 52667c859fe33f70c2e711cb81bbd505d5eb8e75` (git)
  - affected: `96298f640104e4cd9a913a6e50b0b981829b94ff to before 9a21a631ee034b1573dce14b572a24943dbfd7ae` (git)
  - affected: `96298f640104e4cd9a913a6e50b0b981829b94ff to before 900e4db5385ec2cacd372345a80ab9c8e105b3a3` (git)
  - affected: `96298f640104e4cd9a913a6e50b0b981829b94ff to before 042e2cd4bb11e5313b19b87593616524949e4c52` (git)
  - affected: `96298f640104e4cd9a913a6e50b0b981829b94ff to before 25f420a0d4cfd61d3d23ec4b9c56d9f443d91377` (git)
  - affected: `4ad03ff6f680681c5f78254e37c4c856fa953629` (git)
  - affected: `b7d0ca715c1008acd2fc018f02a56fed88f78b75` (git)
  - affected: `799263eb37a4f7f6d39334046929c3bc92452a7f` (git)
  - affected: `8828622fb9b4201eeb0870587052e3d834cfaf61` (git)
  - and 6 more
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.7`
  - unaffected: `before 5.7` (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.131 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.80 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.21 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19.11 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

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

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

## Timeline

- 22 Apr 2026, 13:54 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-31498)
- 22 Apr 2026, 14:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-31498)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/9760b83cfd24b38caee663f429011a0dd6064fa9>
- <https://git.kernel.org/stable/c/de37e2655b7abc3f59254c6b72256840f39fc6d5>
- <https://git.kernel.org/stable/c/e7aab23b7df89a3d754a5f0a7d2237548b328bd0>
- <https://git.kernel.org/stable/c/52667c859fe33f70c2e711cb81bbd505d5eb8e75>
- <https://git.kernel.org/stable/c/9a21a631ee034b1573dce14b572a24943dbfd7ae>
- <https://git.kernel.org/stable/c/900e4db5385ec2cacd372345a80ab9c8e105b3a3>
- <https://git.kernel.org/stable/c/042e2cd4bb11e5313b19b87593616524949e4c52>
- <https://git.kernel.org/stable/c/25f420a0d4cfd61d3d23ec4b9c56d9f443d91377>

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

---

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