Answer in brief
CVE-2026-93076 records a Unknown severity vulnerability in dax/fsdev: clear vmemmap_shift when binding static pgmap. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d5406bd458b0ac10b1301a4d5801d85c8f648637 <d298a0513aaf7d48f2a9f4a90041de910750cfcf || >=d5406bd458b0ac10b1301a4d5801d85c8f648637 <e0239229931faf9ca3367e3befcf16f77b2cd45b | d298a0513aaf7d48f2a9f4a90041de910750cfcf, e0239229931faf9ca3367e3befcf16f77b2cd45b |
| Linux/Linuxgeneric | 7.1 | Not reported |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.