nfc: hci: fix out-of-bounds read in HCP header parsing
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
3.5
References 8
git.kernel.org
- stable/c/ed6d5d97dad0334a7f43d218753429cbe2f70a4f
- stable/c/b99366d74b535d0cadb1ef73e04639415d9ff3b7
- stable/c/37382293f174b82a0616c8295e32b1fc8e13d1ed
- stable/c/c4cc6b3b0013acb3ed0b2b60e57dfae98647fe98
- stable/c/1905f5ec3641b2b234bb63549c8ca11ab85466eb
- stable/c/22d41b176b9989efd21c3b2d3abf6728f05b9d9a
- stable/c/83b1362edc9d6ae376c6f36da116e2c70f2e70a6
- stable/c/f040e590c035bfd9553fe79ee9585caf1b14d67b