CVE-2026-99677: xfs: clamp the pNFS layout range to the maximum file size

Published Nov 20, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

xfs: clamp the pNFS layout range to the maximum file size

xfsfsmapblocks() lets two bad layout ranges through. An offset of 2^63 or more is negative and passes "offset > limit". A length above the limit, such as NFS4UINT64MAX, wraps "offset > limit - length" and stays unclamped. With NFS4UINT64MAX, a read layout is built from an uninitialized mapping.

Reject a negative offset and one at the limit, and clamp the length. This needs "xfs: cap the block count of xfsiomapwritedirect() at one extent".

Affected Software

3 affected componentsFixes available
linux/kernel>=4.0.0<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch xfs: clamp the pNFS layout range to the maximum file size

Frequently Asked Questions

1

Which systems are exposed to this issue?

Systems using the Linux kernel with XFS and pNFS layout handling are relevant. The vulnerable path is associated with processing layout ranges for XFS files.

2

What request values are needed to trigger the flawed range handling?

A layout offset of 2^63 or greater can be interpreted as negative and bypass the existing offset check. A length above the permitted limit, including NFS4_UINT64_MAX, can cause arithmetic wraparound and avoid clamping.

3

What is the observable impact of the NFS4_UINT64_MAX length case?

With NFS4_UINT64_MAX, the kernel can build a read layout from an uninitialized mapping.

4

What should be done if patching cannot be applied immediately?

The provided information does not specify a workaround. Reducing exposure to untrusted pNFS layout requests may be appropriate, but no supported mitigation is stated in the available data.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203