CVE-2026-64357: Linux kernel · xfs: fix exchmaps reservation limit check
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in c597c8580d50127fc1221b5a5b653a94d49e23e3 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 17:04 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- 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-11-06.
- Patch
- Available – fixed in c597c8580d50127fc1221b5a5b653a94d49e23e3, a62ef2d13d6e7270dd5e88c6082bf2d0edcd5112, 4707344b0d36d1012c8a1716e20167cd3afdd5f1 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 6 Nov 2026.
What to do
Upgrade Linux kernel to c597c8580d50127fc1221b5a5b653a94d49e23e3, a62ef2d13d6e7270dd5e88c6082bf2d0edcd5112, 4707344b0d36d1012c8a1716e20167cd3afdd5f1 or 0a5213bbff62b51c7d4999ac8c7e11ea57d00d45.
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– |
Description
In the Linux kernel, the following vulnerability has been resolved: xfs: fix exchmaps reservation limit check xfs_exchmaps_estimate_overhead() adds the bmbt and rmapbt overhead to a local resblks variable, but the final UINT_MAX check still tests req->resblks. That is the reservation value from before the overhead was added. The computed value is stored back in req->resblks and later passed to xfs_trans_alloc(), whose block reservation argument is unsigned int. Check the computed reservation so the existing limit applies to the value that will be used.
References
- git.kernel.org/stable/c/c597c8580d50127fc1221b5a5b653a94d49e23e3 (opens in a new tab)
- git.kernel.org/stable/c/a62ef2d13d6e7270dd5e88c6082bf2d0edcd5112 (opens in a new tab)
- git.kernel.org/stable/c/4707344b0d36d1012c8a1716e20167cd3afdd5f1 (opens in a new tab)
- git.kernel.org/stable/c/0a5213bbff62b51c7d4999ac8c7e11ea57d00d45 (opens in a new tab)