Bug 2554938 (CVE-2026-98575) - CVE-2026-98575 kernel: nfc: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid()
Summary: CVE-2026-98575 kernel: nfc: pn533: fix OOB read in pn533_acr122_is_rx_frame_v...
Keywords:
Status: NEW
Alias: CVE-2026-98575
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-18 15:33 UTC by OSIDB Bzimport
Modified: 2026-10-20 03:28 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-10-18 15:33:58 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.