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-98582nfc: st21nfca: validate received frame size

Description

In the Linux kernel, the following vulnerability has been resolved: nfc: st21nfca: validate received frame size st21nfca_hci_i2c_repack() trims a received frame at its EOF marker before removing byte stuffing. It then assumes the truncated frame contains the LLC header and two CRC bytes, and it unconditionally reads the byte after an escape marker. A malformed frame can place EOF immediately after the start marker or can end its data portion with an escape marker. The former leaves too few bytes for check_crc(), while the latter makes the unstuffing loop read past the current skb length. Require the minimum framing bytes both before and after unstuffing. Use separate input and output cursors while removing byte stuffing, and reject an escape marker without its encoded byte. This keeps malformed frames within the received frame boundary before CRC processing.

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.22% · top 88% of all CVEs (18 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 3096e25a3e40b73afd59e46f3bf8d84f919992a1 – < 8934d2889ae16a7c77520e002398d0689c1ecea5
    • affected 3096e25a3e40b73afd59e46f3bf8d84f919992a1 – < d0596ee6c4b928a5c288790522a7495ee867da72
    • affected 3096e25a3e40b73afd59e46f3bf8d84f919992a1 – < f526c218a149a30f110ce434ff17e033042404b8
    • affected 3096e25a3e40b73afd59e46f3bf8d84f919992a1 – < d4008c3499dba7829bfe002edd99a8bff8ae3a7c
    • affected 3096e25a3e40b73afd59e46f3bf8d84f919992a1 – < 91be5161f37b0a2795ad6806d69be5fa74522e5c
    • affected 3096e25a3e40b73afd59e46f3bf8d84f919992a1 – < 57919d0662d8856211b794140172e51ca389f23d
    • affected 3096e25a3e40b73afd59e46f3bf8d84f919992a1 – < 7b996cc06dda54c02a5aa607bda01109f0ac51e6
    • affected 3096e25a3e40b73afd59e46f3bf8d84f919992a1 – < a653c01ce447f10c36b901646888c0330363af4f
  • Linux · Linux

    • affected 3.16
    • unaffected < 3.16
    • 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-98582 badge
[![CVE-2026-98582](https://cveledger.app/badge/CVE-2026-98582.svg)](https://cveledger.app/cve/CVE-2026-98582)

Record last updated .