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-98575nfc: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid()

Description

In the Linux kernel, the following vulnerability has been resolved: nfc: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid() frame->ccid.datalen is read directly from the USB response frame and used, unchecked, as an index into frame->data[]. A malicious or malfunctioning device can set this field to an arbitrary value, causing the driver to read far outside the received buffer. Bound ccid.datalen against the maximum possible ACR122 frame size before using it. This replaces the existing datalen == 0 check, since datalen < 2 already covers that case and additionally rejects datalen == 1, which would still underflow the "datalen - 2" offset used below.

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 (15 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 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc – < 8db3b1e012a8b25078dfa1efabe3d0cd2916dcba
    • affected 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc – < 74b3fbc60907ee97e3af3249091f57351b53a6d6
    • affected 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc – < 8a0f1bb790d964893db7fc59febda9a534db07b3
    • affected 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc – < ea82b7576793219fa10a8b545f8338998b2a9ce2
    • affected 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc – < 72b8b2126e854d6756a1aa4bdc66d7457b832294
    • affected 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc – < e72cbedc4596e808d22dd2b9fff666ece76f8dd6
    • affected 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc – < 2450a388367231fb7dd798538f393af227c00c4d
    • affected 9815c7cf22daceabfb919ddcd6f2c80e049c1fbc – < b61732f47316d45f27706db7812950145d3327b5
  • Linux · Linux

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

Record last updated .