nfc: pn533: purge fragmented skbs during cleanup
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 963a82e07d4e1f95fc423d53912ac0a7fe643b1c · < 2f5d093194ec24d7c29b91bf7df014924e0f4ea1| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s PN533 NFC driver fails to release queued transmit fragments during cleanup, leaking memory if the device is removed while fragments remain queued. The input does not describe an attacker exploit path or specify network access, authentication, or user-interaction requirements.
Engineers running Linux kernels with the PN533 NFC driver should check their kernel versions; affected versions are not specified.