CVE-2026-93076
dax/fsdev: clear vmemmap_shift when binding static pgmap
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 7.2.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: dax/fsdev: clear vmemmap_shift when binding static pgmap Clear pgmap->vmemmap_shift for static DAX devices. When rebinding a static device from device_dax (which may set vmemmap_shift based on alignment) to fsdev_dax, the stale vmemmap_shift persists on the shared pgmap. Explicitly zero it before devm_memremap_pages() so the vmemmap is built for order-0 folios as fsdev requires.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From d5406bd458b0ac10b1301a4d5801d85c8f648637 · fixed in d298a0513aaf7d48f2a9f4a90041de910750cfcf; From d5406bd458b0ac10b1301a4d5801d85c8f648637 · fixed in e0239229931faf9ca3367e3befcf16f77b2cd45b
- Linux Linux
7.1
- KernelLinux
From 7.1.0 · fixed in 7.2.6