nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers
- 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, 4.20, 5.5, 5.15.218, 6.1.185, and 5 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: llcp: fix OOB read and u8 offset wrap in TLV parsers nfc_llcp_parse_gb_tlv() and nfc_llcp_parse_connection_tlv() contain three related bugs in their TLV parsing loops: 1. 'offset' is declared u8 but tlv_array_len is u16. When TLV data advances offset past 255 it silently wraps to zero, causing infinite loops or double-processing of buffer data. 2. Before reading tlv[0] (type) and tlv[1] (length) there is no check that offset+2 <= tlv_array_len. A truncated TLV causes an OOB read of one byte past the buffer end. 3. After reading the length field, the value bytes are accessed without checking offset+2+length <= tlv_array_len. A crafted length=0xFF on a short buffer causes up to 255 bytes of OOB read past the buffer end. Both functions are reachable without authentication via nfc_llcp_set_remote_gb() which feeds remote LLCP general bytes directly into nfc_llcp_parse_gb_tlv() with no additional validation. Fix all three issues by widening offset from u8 to u16 and adding bounds checks for both the TLV header and value field before each access.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 0be9de2ea01e8d52646e7310a7eef5459cf07ea8 · fixed in 2c1456fe09ab1a5a9fe1d8339ca6d509589b56e1; From 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 · fixed in 7f6f3d087c67a4346189ef2c36481455bbc59a74; From 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 · fixed in 9c47d667963542c3cf8e3007b7f10c0904d08238; From 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 · fixed in a209334ed929941b20810c17c3a507445b0a7c85; From 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 · fixed in 382eaa770335acf4f16a5a55524500f2bb4207df; From 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 · fixed in 2d239590d1845a706304833d40dd6d4fec20ad88; From 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 · fixed in e84cdfdc4a6c88e8b751144458f2e04e24415a28; From 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 · fixed in 875285a165fd3b402de2ab3be0deb355d6f4caf5; From 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 · fixed in 78b20c8eeacd2e44a2d8a4cb5316d3c521d90911; From 5.10.188 · fixed in 5.10.267; From 4.19.291 · fixed in 4.20; From 5.4.251 · fixed in 5.5
- Linux Linux
5.15
- KernelLinux
fixed in 5.10.267; From 5.11.0 · fixed in 5.15.218; From 5.15.0 · fixed in 6.1.185; From 5.16.0 · fixed in 6.6.154; From 6.2.0 · fixed in 6.12.106; From 6.7.0 · fixed in 6.18.47; From 6.13.0 · fixed in 7.1.11; From 6.19.0 · fixed in 7.2.1
References 9
git.kernel.org
- stable/c/2c1456fe09ab1a5a9fe1d8339ca6d509589b56e1
- stable/c/7f6f3d087c67a4346189ef2c36481455bbc59a74
- stable/c/9c47d667963542c3cf8e3007b7f10c0904d08238
- stable/c/a209334ed929941b20810c17c3a507445b0a7c85
- stable/c/382eaa770335acf4f16a5a55524500f2bb4207df
- stable/c/2d239590d1845a706304833d40dd6d4fec20ad88
- stable/c/e84cdfdc4a6c88e8b751144458f2e04e24415a28
- stable/c/875285a165fd3b402de2ab3be0deb355d6f4caf5
- stable/c/78b20c8eeacd2e44a2d8a4cb5316d3c521d90911