CVE-2026-92487

published 17 Sep 2026 · updated 19 Oct 2026

exfat: fix valid_size extension over a shared writable mapping

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1135704ed22f54873eb0498a232611d9eca30dd4 and Kernel 24f20986b253c3e4eb13ebe3c2007d1d352408a6.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=7.2, >=82a81a7352bcf5f2756ac33d47ee0582737e9a85 <1135704ed22f54873eb0498a232611d9eca30dd4, >=82a81a7352bcf5f2756ac33d47ee0582737e9a85 <24f20986b253c3e4eb13ebe3c2007d1d352408a61135704ed22f54873eb0498a232611d9eca30dd4, 24f20986b253c3e4eb13ebe3c2007d1d352408a6

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-92487 severity on Zeptric[![CVE-2026-92487](https://zeptric.io/badge/cve/CVE-2026-92487.svg)](https://zeptric.io/cve/CVE-2026-92487)