nfc: st21nfca: validate ATR_REQ length against the received frame
- 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
- Fix
- Fixed in 5.10.267, 5.15.218, 6.1.185, 6.6.154, 6.12.106, and 3 more
- 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: st21nfca: validate ATR_REQ length against the received frame st21nfca_tm_recv_atr_req() checks that the received ATR_REQ frame is at least ST21NFCA_ATR_REQ_MIN_SIZE and that the self-declared atr_req->length is at least sizeof(struct st21nfca_atr_req), but never checks that atr_req->length does not exceed the actual received length (skb->len). st21nfca_tm_send_atr_res() then trusts the declared length: gb_len = atr_req->length - sizeof(struct st21nfca_atr_req); ... memcpy(atr_res->gbi, atr_req->gbi, gb_len); so an RF peer that sends a short frame but sets atr_req->length larger than the frame makes gb_len exceed the general bytes actually present, and the memcpy reads out of bounds past the received skb. Those bytes are placed in the ATR_RES and sent back to the peer (kernel-memory disclosure to a proximity attacker); a larger declared length is an out-of-bounds read (DoS). Reject frames whose declared length exceeds the received length. The adjacent nfc_tm_activated() path in the same function already derives its general-bytes length from skb->len rather than the declared field. Found by 0sec (https://0sec.ai) using automated source analysis; the missing bound is evident from source. Compile-tested.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 1892bf844ea0261736bd5e75546fc996e9daeedf · fixed in 785df00bb3ae3206674a43284eb06dac575b5c64; From 1892bf844ea0261736bd5e75546fc996e9daeedf · fixed in 2c1ad291f4cdc357f9527b688c6fda9c6ffa7890; From 1892bf844ea0261736bd5e75546fc996e9daeedf · fixed in dd26d30f40c43ad9cfe2f25c6ea0ead1dd51d5aa; From 1892bf844ea0261736bd5e75546fc996e9daeedf · fixed in 9635507fe82949e429b3cd938876a9917125b151; From 1892bf844ea0261736bd5e75546fc996e9daeedf · fixed in 0f344944c506b4f02d2b098489f7268b438c369e; From 1892bf844ea0261736bd5e75546fc996e9daeedf · fixed in bfcca5f42c9aa4eadef1e5fe7bb23783d7fcc96d; From 1892bf844ea0261736bd5e75546fc996e9daeedf · fixed in 304f5b414f4051d324b8c4a3ab0e79f7dc7e150e; From 1892bf844ea0261736bd5e75546fc996e9daeedf · fixed in f33cecf69095c43be88567fef92b180b858f7369; From 1892bf844ea0261736bd5e75546fc996e9daeedf · fixed in 5cdcca5d62a66eda6b774110a44cba67bc1a8d1d
- Linux Linux
3.17
- KernelLinux
From 3.17.0 · fixed in 5.10.267; From 5.11.0 · fixed in 5.15.218; From 5.16.0 · fixed in 6.1.185; From 6.2.0 · fixed in 6.6.154; From 6.7.0 · fixed in 6.12.106; From 6.13.0 · fixed in 6.18.47; From 6.19.0 · fixed in 7.1.11; From 7.2.0 · fixed in 7.2.1
References 9
git.kernel.org
- stable/c/785df00bb3ae3206674a43284eb06dac575b5c64
- stable/c/2c1ad291f4cdc357f9527b688c6fda9c6ffa7890
- stable/c/dd26d30f40c43ad9cfe2f25c6ea0ead1dd51d5aa
- stable/c/9635507fe82949e429b3cd938876a9917125b151
- stable/c/0f344944c506b4f02d2b098489f7268b438c369e
- stable/c/bfcca5f42c9aa4eadef1e5fe7bb23783d7fcc96d
- stable/c/304f5b414f4051d324b8c4a3ab0e79f7dc7e150e
- stable/c/f33cecf69095c43be88567fef92b180b858f7369
- stable/c/5cdcca5d62a66eda6b774110a44cba67bc1a8d1d