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-80797nfc: pn533: purge fragmented skbs during cleanup

Description

In the Linux kernel, the following vulnerability has been resolved: nfc: pn533: purge fragmented skbs during cleanup pn53x_common_clean() purges resp_q before freeing the common PN533 state, but it leaves fragment_skb untouched. The fragmentation helpers queue transmit fragments there while sending large initiator or target-mode frames, and those skbs remain owned by the driver until they are sent or discarded. If the device is removed while fragments are still queued, the common cleanup path frees the PN533 state without releasing the queued fragment skbs, leaking them. Purge fragment_skb during cleanup alongside resp_q.

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 (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 963a82e07d4e1f95fc423d53912ac0a7fe643b1c – < 130b5ad4492f8e53d0398ee3af2b0e2388504d11
    • affected 963a82e07d4e1f95fc423d53912ac0a7fe643b1c – < 9319c3c4962efc8697246b563ea31c6d47f085aa
    • affected 963a82e07d4e1f95fc423d53912ac0a7fe643b1c – < d63e85c5d5555fe6aa65155d3a09452597e163c3
    • affected 963a82e07d4e1f95fc423d53912ac0a7fe643b1c – < 4a52ec2457ff8c26206fcc20fa1972cc35a678c4
    • affected 963a82e07d4e1f95fc423d53912ac0a7fe643b1c – < e169277281373818ae1cedf976aa1e99118fb77d
    • affected 963a82e07d4e1f95fc423d53912ac0a7fe643b1c – < 2f5d093194ec24d7c29b91bf7df014924e0f4ea1
    • affected 963a82e07d4e1f95fc423d53912ac0a7fe643b1c – < e7ed2ea5590fbe2d3be39ee4fb0c758a12e31d0c
    • affected 963a82e07d4e1f95fc423d53912ac0a7fe643b1c – < e95beff58b38c871c557bf84e528408283c2c0ad
    • affected 963a82e07d4e1f95fc423d53912ac0a7fe643b1c – < 5718fc62198c38c2de5316020a90506f9e75e0bb
  • Linux · Linux

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

Record last updated .