Kernel memory exposure via undersized XDomain packets
Published Jun 25, 2026 · Updated Jun 25, 2026
Out-of-bounds reads in the Linux Kernel Thunderbolt XDomain handler allow physically proximate attackers to expose kernel memory. The tb_xdp_handle_request() function accepts a packet after only a generic header-length check, then casts its kmemdup buffer to larger protocol-specific structures without checking the allocation size. XDomain must be enabled or allowed and a malicious Thunderbolt or USB4 peer must be connected; repeated malformed requests can expose adjacent heap data or interrupt the host through a kernel fault.
Summary
What happened
Out-of-bounds reads in the Linux Kernel Thunderbolt XDomain handler allow physically proximate attackers to expose kernel memory. The tb_xdp_handle_request() function accepts a packet after only a generic header-length check, then casts its kmemdup buffer to larger protocol-specific structures without checking the allocation size. XDomain must be enabled or allowed and a malicious Thunderbolt or USB4 peer must be connected; repeated malformed requests can expose adjacent heap data or interrupt the host through a kernel fault.
The record
- CVE
- CVE-2026-53147
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-125, T1200
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 25, 2026CVE publishedPublication date reported by the CVE source.
- Jun 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.15
- Affected versionversion=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <07cd2787cdf8942d24a1a3ef81aa89b526fb6381
- Affected versionversion=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <0dd61ba03d05187726ecdf9c0e2175a81b9b24f6
- Affected versionversion=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <46da5c3ea011e884028a91cf913db093920a915b
- Affected versionversion=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <79235c8add5da4bf27a12f5a5dbb579f300c059e
- Affected versionversion=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <a504b9f2797b739e0304d537e8aa4ce883ecce39
- Affected versionversion=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <a770e62923090d7572f1f5a8507ae551d354a057
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo