Strix
73.2K

CVE-2026-80797

UnknownEPSS 0.24%

Last modified

CVE-2026-80797 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.24% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.24%

14.4th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 963a82e07d4e1f95fc423d53912ac0a7fe643b1c, < 130b5ad4492f8e53d0398ee3af2b0e2388504d11; >= 963a82e07d4e1f95fc423d53912ac0a7fe643b1c, < 9319c3c4962efc8697246b563ea31c6d47f085aa; >= 963a82e07d4e1f95fc423d53912ac0a7fe643b1c, < d63e85c5d5555fe6aa65155d3a09452597e163c3; >= 963a82e07d4e1f95fc423d53912ac0a7fe643b1c, < 4a52ec2457ff8c26206fcc20fa1972cc35a678c4; >= 963a82e07d4e1f95fc423d53912ac0a7fe643b1c, < e169277281373818ae1cedf976aa1e99118fb77d; >= 963a82e07d4e1f95fc423d53912ac0a7fe643b1c, < 2f5d093194ec24d7c29b91bf7df014924e0f4ea1; >= 963a82e07d4e1f95fc423d53912ac0a7fe643b1c, < e7ed2ea5590fbe2d3be39ee4fb0c758a12e31d0c; >= 963a82e07d4e1f95fc423d53912ac0a7fe643b1c, < e95beff58b38c871c557bf84e528408283c2c0ad; >= 963a82e07d4e1f95fc423d53912ac0a7fe643b1c, < 5718fc62198c38c2de5316020a90506f9e75e0bb
LinuxLinux3.12

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-80797?
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.
How severe is CVE-2026-80797?
Severity scoring for CVE-2026-80797 is pending analysis. The EPSS model estimates a 0.24% probability of exploitation in the next 30 days.
How do I fix CVE-2026-80797?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-80797?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST