CVE-2026-99678: xfs: cap the block count of xfs_iomap_write_direct() at one extent
In the Linux kernel, the following vulnerability has been resolved:
xfs: cap the block count of xfsiomapwritedirect() at one extent
xfsiomapwritedirect() 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.
xfsbmapiwrite() maps at most XFSMAXBMBTEXTLEN blocks here, so cap the count at that. nfsd asks again for the rest. The other callers get the same mapping as before.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.3.5-1 - Compensating control
Cap the block count reserved by xfs_iomap_write_direct() at one extent.
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
Systems using XFS with pNFS layouts are exposed when an NFS client can request an excessively large RW LAYOUTGET. The vulnerable path is xfs_iomap_write_direct() in the Linux kernel.
What does an attacker or client need to do to trigger the failure?
A pNFS client must choose a sufficiently large block count for an RW LAYOUTGET; the described case is a 16 TiB request. That count can wrap the unsigned-int block reservation, causing XFS to shut down.
What is the mitigation if the fix cannot be applied immediately?
The provided information identifies pNFS layout handling as the affected scenario. Limiting or avoiding excessively large RW LAYOUTGET requests from pNFS clients reduces exposure, but no specific configuration workaround is provided.