CVE-2026-53146: Linux kernel · Out-of-bounds Read
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 7.1 High · fixed in fc261397295b8ad0654cec747b0ec25ea0011995 : patch Linux kernel soon.
Data as of 26 Oct 2026, 17:30 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in fc261397295b8ad0654cec747b0ec25ea0011995, c55da494dfb445fb28df3a9d293c2be6a299cd01, b5daa920f44cb582272fc9bfaeb67408776cbaef +5
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: thunderbolt: Limit XDomain response copy to actual frame size tb_xdomain_copy() copies req->response_size bytes from the received packet buffer regardless of the actual frame size. When a short response arrives, this reads past the valid frame data in the DMA pool buffer into stale contents from previous transactions. Use the minimum of frame size and expected response size for the copy length.
References
- git.kernel.org/stable/c/c55da494dfb445fb28df3a9d293c2be6a299cd01 (opens in a new tab)
- git.kernel.org/stable/c/7720654b4842bcdfeb64bc002f6186041849e1e7 (opens in a new tab)
- git.kernel.org/stable/c/033dfa63bf6be2653441a1dccae4a8313a91bb9d (opens in a new tab)
- git.kernel.org/stable/c/fc261397295b8ad0654cec747b0ec25ea0011995 (opens in a new tab)
- git.kernel.org/stable/c/a15b6d3136accb2bf84b04d9a3ddd991f7fbf1cb (opens in a new tab)
- git.kernel.org/stable/c/b5daa920f44cb582272fc9bfaeb67408776cbaef (opens in a new tab)
- git.kernel.org/stable/c/b2c1e5d9f1598cc1a4736d5c6bd1218f90805ee4 (opens in a new tab)
- git.kernel.org/stable/c/4db2bd2ed4785dbadaeeab9f4e346b21ac5fb8eb (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-784472.html (opens in a new tab)