Kernel memory overwrite via oversized XDomain response
Published Jun 25, 2026 · Updated Jun 25, 2026
Out-of-bounds write in Linux Kernel allows physically proximate attackers to corrupt kernel memory through an XDomain response. In tb_xdp_properties_request(), a response-controlled packet length drives memcpy past a kcalloc buffer because it is not clamped to the declared data_length. Reachability requires an attacker-controlled Thunderbolt XDomain peer; the overwrite can crash the kernel or corrupt kernel-resident data, but code execution is not established.
Summary
What happened
Out-of-bounds write in Linux Kernel allows physically proximate attackers to corrupt kernel memory through an XDomain response. In tb_xdp_properties_request(), a response-controlled packet length drives memcpy past a kcalloc buffer because it is not clamped to the declared data_length. Reachability requires an attacker-controlled Thunderbolt XDomain peer; the overwrite can crash the kernel or corrupt kernel-resident data, but code execution is not established.
The record
- CVE
- CVE-2026-53148
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- Unavailable
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 <05a43157676c243c248d1c6d9dcecbe6eba2f35d
- Affected versionversion=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <0b334279a82d79fb4723bd4f614305de1ab69caa
- Affected versionversion=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <322e93448d908434ae5545660fcbe8f5a7a8e141
- Affected versionversion=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <5db10c8ad8c09f72c847dfeef3d876098257f505
- Affected versionversion=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <6021d39ccd979713b39b980286020d8f9a45efd1
- Affected versionversion=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <89ae04365e01d5ae4aae83044a8bbd2a9aaf8d0d
- Affected versionversion=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <906035d5c3784570191d259cbf9a0ac1617852b5
- Affected versionversion=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <fcbd0cdab92838854a5818be7ed8a097164ef6d5
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.
Weakness, pattern, technique
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