thunderbolt: property: Reject u32 wrap in tb_property_entry_valid()
- 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.259, 5.15.210, 6.1.176, 6.6.143, 6.12.93, and 2 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
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: thunderbolt: property: Reject u32 wrap in tb_property_entry_valid() entry->value is u32 and entry->length is u16; the sum is performed in u32 and wraps. A malicious XDomain peer can pick value = 0xffffff00, length = 0x100 so the sum 0x100000000 wraps to 0 and passes the > block_len check. tb_property_parse() then passes entry->value to parse_dwdata() as a dword offset into the property block, reading attacker-directed memory far past the allocation. For TEXT-typed entries with the "deviceid" or "vendorid" keys this lands in xd->device_name / xd->vendor_name and is readable back via the per-XDomain device_name / vendor_name sysfs attributes; the leak is NUL-bounded (kstrdup() stops at the first zero byte) and untargeted (the attacker picks a delta, not an absolute address). DATA-typed entries are parsed into property->value.data but not generically surfaced to userspace. Use check_add_overflow() so a wrapped sum is rejected.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From cdae7c07e3e3509eaabc18c1640a55dc5b99c179 · fixed in 6a63623621639acbb39bc2d9fb09559681716695; From cdae7c07e3e3509eaabc18c1640a55dc5b99c179 · fixed in e8a0b0a93a6ef958e70b1dd4930beb6dc0026b36; From cdae7c07e3e3509eaabc18c1640a55dc5b99c179 · fixed in 9fee50c4e1e42f6d3cbe30df584f9f648f626071; From cdae7c07e3e3509eaabc18c1640a55dc5b99c179 · fixed in 8d4a758b407ab3de3be86d1ceadfa35d717d30c7; From cdae7c07e3e3509eaabc18c1640a55dc5b99c179 · fixed in 5c06a3043ad944f087bb2ae0aae28d820bb9f460; From cdae7c07e3e3509eaabc18c1640a55dc5b99c179 · fixed in 31b98e503ecca8077e5247253dd5425ab84bc96d; From cdae7c07e3e3509eaabc18c1640a55dc5b99c179 · fixed in a47784aee77f33f786dc5d7375db821bdae68792; From cdae7c07e3e3509eaabc18c1640a55dc5b99c179 · fixed in 01deda0152066c6c955f0619114ea6afa070aaec
- Linux Linux
4.15
- KernelLinux
From 4.15.0 · fixed in 5.10.259; From 5.11.0 · fixed in 5.15.210; From 5.16.0 · fixed in 6.1.176; From 6.2.0 · fixed in 6.6.143; From 6.7.0 · fixed in 6.12.93; From 6.13.0 · fixed in 6.18.35; From 6.19.0 · fixed in 7.0.12
References 8
git.kernel.org
- stable/c/6a63623621639acbb39bc2d9fb09559681716695
- stable/c/e8a0b0a93a6ef958e70b1dd4930beb6dc0026b36
- stable/c/9fee50c4e1e42f6d3cbe30df584f9f648f626071
- stable/c/8d4a758b407ab3de3be86d1ceadfa35d717d30c7
- stable/c/5c06a3043ad944f087bb2ae0aae28d820bb9f460
- stable/c/31b98e503ecca8077e5247253dd5425ab84bc96d
- stable/c/a47784aee77f33f786dc5d7375db821bdae68792
- stable/c/01deda0152066c6c955f0619114ea6afa070aaec