CVE-2026-80797

nfc: pn533: purge fragmented skbs during cleanup

N/A
Published: September 4, 2026 at 03:13 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.12963a82e07d4e1f95fc423d53912ac0a7fe643b1c
Vendor states this is fixed in 130b5ad4492f8e53d0398ee3af2b0e2388504d11 (fixed)
Vendor states this is fixed in 2f5d093194ec24d7c29b91bf7df014924e0f4ea1 (fixed)
Vendor states this is fixed in 4a52ec2457ff8c26206fcc20fa1972cc35a678c4 (fixed)
Vendor states this is fixed in 5718fc62198c38c2de5316020a90506f9e75e0bb (fixed)
Vendor states this is fixed in 9319c3c4962efc8697246b563ea31c6d47f085aa (fixed)
Vendor states this is fixed in d63e85c5d5555fe6aa65155d3a09452597e163c3 (fixed)
Vendor states this is fixed in e169277281373818ae1cedf976aa1e99118fb77d (fixed)
Vendor states this is fixed in e7ed2ea5590fbe2d3be39ee4fb0c758a12e31d0c (fixed)
Vendor states this is fixed in e95beff58b38c871c557bf84e528408283c2c0ad (fixed)
Vendor states this is fixed in 3.12 (unaffected)
Vendor states this is fixed in 5.10.267 (unaffected)
Vendor states this is fixed in 5.15.218 (unaffected)
Vendor states this is fixed in 6.1.185 (unaffected)
Vendor states this is fixed in 6.12.106 (unaffected)
Vendor states this is fixed in 6.18.47 (unaffected)
Vendor states this is fixed in 6.6.154 (unaffected)
Vendor states this is fixed in 7.1.11 (unaffected)
Vendor states this is fixed in 7.2.1 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card