CVE-2026-23252: Linux kernel · xfs: get rid of the xchk_xfile_*_descr calls
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 60382993a2e18041f88c7969f567f168cd3b4de3 : update Linux kernel when convenient.
Data as of 5 Nov 2026, 22: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-05.
- Patch
- Available – fixed in 60382993a2e18041f88c7969f567f168cd3b4de3, 695455fbc49053cbf555f2f302a5dcd600f412ff, 18e9cf2259b4157fd282b323514375f2f6a59edb +1
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Mar 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 5 Nov 2026.
What to do
Upgrade Linux kernel to 60382993a2e18041f88c7969f567f168cd3b4de3, 695455fbc49053cbf555f2f302a5dcd600f412ff, 18e9cf2259b4157fd282b323514375f2f6a59edb or 2d8afee89262762fe0e5547772708c75f320c957.
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: get rid of the xchk_xfile_*_descr calls The xchk_xfile_*_descr macros call kasprintf, which can fail to allocate memory if the formatted string is larger than 16 bytes (or whatever the nofail guarantees are nowadays). Some of them could easily exceed that, and Jiaming Zhang found a few places where that can happen with syzbot. The descriptions are debugging aids and aren't required to be unique, so let's just pass in static strings and eliminate this path to failure. Note this patch touches a number of commits, most of which were merged between 6.6 and 6.14.
References
- git.kernel.org/stable/c/695455fbc49053cbf555f2f302a5dcd600f412ff (opens in a new tab)
- git.kernel.org/stable/c/18e9cf2259b4157fd282b323514375f2f6a59edb (opens in a new tab)
- git.kernel.org/stable/c/2d8afee89262762fe0e5547772708c75f320c957 (opens in a new tab)
- git.kernel.org/stable/c/60382993a2e18041f88c7969f567f168cd3b4de3 (opens in a new tab)