Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-97408Bluetooth: L2CAP: validate connectionless PSM length

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: validate connectionless PSM length Connectionless L2CAP frames carry a two-byte PSM at the start of the payload. l2cap_recv_frame() currently reads that PSM unconditionally after validating only the outer L2CAP length. A malformed connectionless frame with a zero- or one-byte payload can therefore make the parser read beyond the advertised skb payload and use tailroom bytes as part of the PSM. A VHCI-backed QEMU reproducer injected a one-byte connectionless payload and reached the unchecked read. Reject connectionless frames that cannot contain the PSM before reading or pulling it. This preserves all valid connectionless frames while dropping only structurally incomplete packets.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 9 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8104cd9859b6de0826cffa68adf2c1461185823b
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 9448e6f693fcf1f0ac4ee648a9b2cc83bfe4a982
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 22fc1ce4e37c81d4e7aac01566ebdc232214540d
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 72e26293a231f63a856340d3a1f0f5fc29bf87e5
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 3502ede8aed3c3ee1786d952a11054ac737d1a38
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < ae69dca122f6d6046a68cf40153e6e827c77ff5c
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a40a5f922546b3bd7c094d882b29177db4f2abe0
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-97408 badge
[![CVE-2026-97408](https://cveledger.app/badge/CVE-2026-97408.svg)](https://cveledger.app/cve/CVE-2026-97408)

Record last updated .