Skip to main content
VulnerabilityPublished Updated

CVE-2026-53146: Linux kernel · Out-of-bounds Read

Affects Linux kernelSource CVE Database V5

0

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

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ cdae7c07e3e3509eaabc18c1640a55dc5b99c179, < fc261397295b8ad0654cec747b0ec25ea0011995
Fixed in
  • fc261397295b8ad0654cec747b0ec25ea0011995
LinuxLinuxAffected
  • ≥ cdae7c07e3e3509eaabc18c1640a55dc5b99c179, < c55da494dfb445fb28df3a9d293c2be6a299cd01
Fixed in
  • c55da494dfb445fb28df3a9d293c2be6a299cd01
LinuxLinuxAffected
  • ≥ cdae7c07e3e3509eaabc18c1640a55dc5b99c179, < b5daa920f44cb582272fc9bfaeb67408776cbaef
Fixed in
  • b5daa920f44cb582272fc9bfaeb67408776cbaef
LinuxLinuxAffected
  • ≥ cdae7c07e3e3509eaabc18c1640a55dc5b99c179, < b2c1e5d9f1598cc1a4736d5c6bd1218f90805ee4
Fixed in
  • b2c1e5d9f1598cc1a4736d5c6bd1218f90805ee4
LinuxLinuxAffected
  • ≥ cdae7c07e3e3509eaabc18c1640a55dc5b99c179, < a15b6d3136accb2bf84b04d9a3ddd991f7fbf1cb
Fixed in
  • a15b6d3136accb2bf84b04d9a3ddd991f7fbf1cb
LinuxLinuxAffected
  • ≥ cdae7c07e3e3509eaabc18c1640a55dc5b99c179, < 7720654b4842bcdfeb64bc002f6186041849e1e7
Fixed in
  • 7720654b4842bcdfeb64bc002f6186041849e1e7

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

Community reviews

Loading reviews…