Live › vulnerability › CVE-2026-98575
Go to dashboardThe pn533 NFC driver in the Linux kernel trusts a length field from an ACR122 USB reader response and uses it as an array index without a bound check. A malicious or malfunctioning USB device can make the driver read memory outside the received buffer.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Only machines running a Linux kernel with the pn533 NFC driver loaded, typically those with a USB NFC reader such as an ACR122 attached. Exposure needs a malicious or faulty USB device plugged into the host, so systems without NFC readers or with the driver blocked are unlikely to be affected. The sources do not say which kernel versions are vulnerable.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
nfc: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid()
frame->ccid.datalen is read directly from the USB response frame and used, unchecked, as an index into frame->data[]. A malicious or malfunctioning device can set this field to an arbitrary value, causing the driver to read far outside the received buffer.
Bound ccid.datalen against the maximum possible ACR122 frame size before using it. This replaces the existing datalen == 0 check, since datalen < 2 already covers that case and additionally rejects datalen == 1, which would still underflow the "datalen - 2" offset used below.
This page as .md · .json · in your agent: get_signal("CVE-2026-98575")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.