CVE Catalog

CVE-2026-93076

Unknown
Published: Translated: NVD NIST

Summary

In the Linux kernel, the dax/fsdev module does not clear pgmap->vmemmap_shift when binding a static DAX device. 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, causing the vmemmap to be built for a different folio order than fsdev requires.

Risk Assessment

This can lead to incorrect memory behavior and potential kernel crashes when rebinding static DAX devices.

Recommendation

Update the Linux kernel to a version with the fix. Avoid rebinding static DAX devices between device_dax and fsdev_dax without updating.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS