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-98457Bluetooth: L2CAP: validate frame length before control and FCS access

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: validate frame length before control and FCS access l2cap_data_rcv() unpacks either a two-byte or four-byte control field without first ensuring that it is present. A short ERTM or streaming-mode frame can therefore cause an out-of-bounds read. There is a second short-frame case when CRC16 is enabled. After the control field is pulled, l2cap_check_fcs() subtracts two from skb->len without checking it. If fewer than two bytes remain, the subtraction wraps; skb_trim() leaves the buffer unchanged and the subsequent FCS load reads past the logical end of the frame. Validate that the frame contains both its control field and, when enabled, its FCS before either field is accessed.

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 1 day 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.18% · top 92% of all CVEs (17 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 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a – < 4373ba79a267947e771c438507f7b103e30bdb21
    • affected 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a – < 965bd88ed4b4763cb765dd65885adcfa588c6b14
    • affected 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a – < 3acf6a0038ec0d4e8f4dcbfc2a557dff5f61cb70
    • affected 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a – < 8c7556c7cd17e073bbefdc4a9a4694a207544c37
    • affected 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a – < 1fdbb2a712a9a162ee817c959740face80b3d929
    • affected 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a – < c6a288e6001bcce16553c3853e0f5a45eaaf85c7
    • affected 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a – < f557274af7b94b6134692e6f26b880f1e34c15bf
    • affected 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a – < 6c78a213d9070b610c7f418af2c25b66180b7e37
  • Linux · Linux

    • affected 2.6.32
    • unaffected < 2.6.32
    • 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.112 – ≤ 6.12.*
    • unaffected 6.18.55 – ≤ 6.18.*
    • unaffected 7.2.9 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .