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-80823nfc: st21nfca: validate ATR_REQ length against the received frame

Description

In the Linux kernel, the following vulnerability has been resolved: nfc: st21nfca: validate ATR_REQ length against the received frame st21nfca_tm_recv_atr_req() checks that the received ATR_REQ frame is at least ST21NFCA_ATR_REQ_MIN_SIZE and that the self-declared atr_req->length is at least sizeof(struct st21nfca_atr_req), but never checks that atr_req->length does not exceed the actual received length (skb->len). st21nfca_tm_send_atr_res() then trusts the declared length: gb_len = atr_req->length - sizeof(struct st21nfca_atr_req); ... memcpy(atr_res->gbi, atr_req->gbi, gb_len); so an RF peer that sends a short frame but sets atr_req->length larger than the frame makes gb_len exceed the general bytes actually present, and the memcpy reads out of bounds past the received skb. Those bytes are placed in the ATR_RES and sent back to the peer (kernel-memory disclosure to a proximity attacker); a larger declared length is an out-of-bounds read (DoS). Reject frames whose declared length exceeds the received length. The adjacent nfc_tm_activated() path in the same function already derives its general-bytes length from skb->len rather than the declared field. Found by 0sec (https://0sec.ai) using automated source analysis; the missing bound is evident from source. Compile-tested.

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 45 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.19% · top 91% 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 1892bf844ea0261736bd5e75546fc996e9daeedf – < 785df00bb3ae3206674a43284eb06dac575b5c64
    • affected 1892bf844ea0261736bd5e75546fc996e9daeedf – < 2c1ad291f4cdc357f9527b688c6fda9c6ffa7890
    • affected 1892bf844ea0261736bd5e75546fc996e9daeedf – < dd26d30f40c43ad9cfe2f25c6ea0ead1dd51d5aa
    • affected 1892bf844ea0261736bd5e75546fc996e9daeedf – < 9635507fe82949e429b3cd938876a9917125b151
    • affected 1892bf844ea0261736bd5e75546fc996e9daeedf – < 0f344944c506b4f02d2b098489f7268b438c369e
    • affected 1892bf844ea0261736bd5e75546fc996e9daeedf – < bfcca5f42c9aa4eadef1e5fe7bb23783d7fcc96d
    • affected 1892bf844ea0261736bd5e75546fc996e9daeedf – < 304f5b414f4051d324b8c4a3ab0e79f7dc7e150e
    • affected 1892bf844ea0261736bd5e75546fc996e9daeedf – < f33cecf69095c43be88567fef92b180b858f7369
    • affected 1892bf844ea0261736bd5e75546fc996e9daeedf – < 5cdcca5d62a66eda6b774110a44cba67bc1a8d1d
  • Linux · Linux

    • affected 3.17
    • unaffected < 3.17
    • unaffected 5.10.267 – ≤ 5.10.*
    • unaffected 5.15.218 – ≤ 5.15.*
    • unaffected 6.1.185 – ≤ 6.1.*
    • unaffected 6.6.154 – ≤ 6.6.*
    • unaffected 6.12.106 – ≤ 6.12.*
    • unaffected 6.18.47 – ≤ 6.18.*
    • unaffected 7.1.11 – ≤ 7.1.*
    • unaffected 7.2.1 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .