CVE-2026-99678: Linux kernel · xfs: cap the block count of xfs_iomap_write_direct() at one extent
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 83e0edb26d05515083784db26a02a809371ccdb3 : update Linux kernel when convenient.
Data as of 20 Nov 2026, 06:04 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 83e0edb26d05515083784db26a02a809371ccdb3, 73b0f3d5201f741125061d8559e9631f1af4cb39, 66d1ce09ebd72709f8d739630c39f440445173fd +1
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 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 19 Nov 2026.
What to do
Upgrade Linux kernel to 83e0edb26d05515083784db26a02a809371ccdb3, 73b0f3d5201f741125061d8559e9631f1af4cb39, 66d1ce09ebd72709f8d739630c39f440445173fd or 7f4972601b3faa66524e44df9e929fd491e35bfd.
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: cap the block count of xfs_iomap_write_direct() at one extent xfs_iomap_write_direct() reserves blocks for the whole count in an unsigned int. For a pNFS layout the client chooses that count, and an RW LAYOUTGET for 16 TiB wraps the reservation and shuts XFS down. xfs_bmapi_write() maps at most XFS_MAX_BMBT_EXTLEN blocks here, so cap the count at that. nfsd asks again for the rest. The other callers get the same mapping as before.
References
- git.kernel.org/stable/c/7f4972601b3faa66524e44df9e929fd491e35bfd (opens in a new tab)
- git.kernel.org/stable/c/73b0f3d5201f741125061d8559e9631f1af4cb39 (opens in a new tab)
- git.kernel.org/stable/c/83e0edb26d05515083784db26a02a809371ccdb3 (opens in a new tab)
- git.kernel.org/stable/c/66d1ce09ebd72709f8d739630c39f440445173fd (opens in a new tab)