nfc: hci: fix out-of-bounds read in HCP header parsing
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 8b8d2e08bf0d50193931afd27482a59376b66b2b · < 22d41b176b9989efd21c3b2d3abf6728f05b9d9a| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nfc: hci: fix out-of-bounds read in HCP header parsing
Both nfc_hci_recv_from_llc() and nci_hci_data_received_cb() read packet->header from skb->data at function entry without first checking that the buffer holds at least one byte. A malicious NFC peer can send a 0-byte HCP frame that passes through the SHDLC layer and reaches these functions, causing an out-of-bounds heap read of packet->header. The same 0-byte frame, if queued as a non-final fragment, also causes the reassembly loop to underflow msg_len to UINT_MAX, triggering skb_over_panic() when the reassembled skb is written.
Fix this by adding a pskb_may_pull() check at the entry of each function before packet->header is first accessed. The existing pskb_may_pull() checks before the reassembled hcp_skb is cast to struct hcp_packet remain in place to guard the 2-byte HCP message header.
From the CVE record · Linux
Linux kernel NFC HCI handlers can read beyond a buffer when they receive a zero-byte HCP frame. A malicious NFC peer can send such a frame through the SHDLC layer; if it is queued as a non-final fragment, it can also trigger skb_over_panic() during reassembly. Authentication and user-interaction requirements are not specified.
Engineers running Linux kernels with NFC HCI support should check their versions; affected versions are not specified.