CVE-2026-98575 nfc: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid()

Q: Is CVE-2026-98575 being exploited?

There is no known exploitation of CVE-2026-98575 in the wild and no public exploit code.

Not scored Published 18 Oct 2026 Updated 19 Oct 2026

A malicious NFC device can trigger an out-of-bounds read in the Linux kernel pn533 driver, potentially leaking memory or causing a crash.

Exploited in the wild: Not known
Login needed: Not needed
Attackable: Local or same network only
Victim action needed: A user has to click or open something
Fix: Available

What is CVE-2026-98575?

CVE-2026-98575 is a memory corruption vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

Official description

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.

Which versions are affected by CVE-2026-98575?

How do I fix CVE-2026-98575?

Apply the vendor's patch.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2026-98575 being exploited?