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.

Fixes: 9815c7cf22 ("NFC: pn533: Separate physical layer from the core implementation")
Reported-by: [email protected]
Closes: https://syzkaller.appspot.com/bug?extid=1853daab1a47603d4678
Tested-by: [email protected]
Assisted-by: LLM
Signed-off-by: Deepanshu Kartikey <[email protected]>
Link: https://patch.msgid.link/[email protected]
Signed-off-by: David Heidelberg <[email protected]>
This commit is contained in:
Deepanshu Kartikey authored and David Heidelberg committed 2026-09-23 22:13:18 +02:00
1 parent 7dcf371a35
commit b61732f473
1 file changed
+3 -1
+3 -1
View File
@@ -319,7 +319,9 @@ static bool pn533_acr122_is_rx_frame_valid(void *_frame, struct pn533 *dev)
if (frame->ccid.type != 0x83)
return false;
if (!frame->ccid.datalen)
if (frame->ccid.datalen < 2 ||
frame->ccid.datalen > PN533_ACR122_FRAME_MAX_PAYLOAD_LEN +
PN533_ACR122_RX_FRAME_TAIL_LEN)
return false;
if (frame->data[frame->ccid.datalen - 2] == 0x63)