VulnerabilityPublished 17 Sep 2026Updated 23 Sep 2026

CVE-2026-93076: Linux kernel · dax/fsdev: clear vmemmap_shift when binding static pgmap

Affects Linux kernelSource GCVE Database

Authoritative record:CVE-2026-93076

Not known to be exploited.

Data as of 26 Oct 2026, 12:55 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 24.04 LTSlinux-aws-6.14`pkg:deb/ubuntu/linux-aws-6.14?arch=source&distro=noble`Other threats	Affected 6.14.0-1007.7~24.04.1 – 6.14.0-1018.18~24.04.1 11 affected builds	Fixed in–
Ubuntu 24.04 LTSlinux-aws-6.17`pkg:deb/ubuntu/linux-aws-6.17?arch=source&distro=noble`Other threats	Affected 6.17.0-1005.5~24.04.2 – 6.17.0-1020.20~24.04.1 10 affected builds	Fixed in–
Ubuntu 24.04 LTSlinux-azure-6.11`pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=noble`Other threats	Affected 6.11.0-1008.8~24.04.1 – 6.11.0-1018.18~24.04.1 7 affected builds	Fixed in–
Ubuntu 24.04 LTSlinux-azure-6.14`pkg:deb/ubuntu/linux-azure-6.14?arch=source&distro=noble`Other threats	Affected 6.14.0-1010.10~24.04.1 – 6.14.0-1017.17~24.04.1 5 affected builds	Fixed in–
Ubuntu 24.04 LTSlinux-azure-6.17`pkg:deb/ubuntu/linux-azure-6.17?arch=source&distro=noble`Other threats	Affected 6.17.0-1008.8~24.04.1 – 6.17.0-1022.22 10 affected builds	Fixed in–
Ubuntu 24.04 LTSlinux-azure-fde-6.14`pkg:deb/ubuntu/linux-azure-fde-6.14?arch=source&distro=noble`Other threats	Affected 6.14.0-1012.12~24.04.1 – 6.14.0-1017.17~24.04.1 5 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix has been applied to the affected Linux kernel versions to clear the vmemmap_shift field properly. Users should update to patched kernel versions to remediate this vulnerability. Since this is not a cloud service, remediation requires applying the updated kernel packages provided by the vendor or distribution maintainers.

Description

A vulnerability in the Linux kernel related to the handling of vmemmap_shift in static DAX devices has been resolved. The issue involves stale vmemmap_shift values persisting when rebinding a static device from device_dax to fsdev_dax, potentially causing incorrect memory mapping. This has been fixed by explicitly clearing vmemmap_shift before memory remapping. The vulnerability affects specific versions of the linux-hwe-edge kernel and is rated medium severity.

Impact

The vulnerability could cause incorrect memory mapping behavior in static DAX devices within the Linux kernel, potentially affecting system stability or functionality related to device memory management. No known exploits are reported in the wild. The impact is assessed as medium severity based on the nature of the memory mapping issue.

Summary

The Linux kernel vulnerability (CVE-2026-93076) concerns the dax/fsdev subsystem where the vmemmap_shift field was not cleared when binding a static pgmap. When a static device is rebound from device_dax, which may set vmemmap_shift based on alignment, to fsdev_dax, the stale vmemmap_shift value remains on the shared pgmap. This can lead to improper construction of the vmemmap for order-0 folios as required by fsdev. The fix involves explicitly zeroing vmemmap_shift before calling devm_memremap_pages(), ensuring correct memory mapping for static DAX devices.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Oct 2026, 23:28 UTC

Technical details

References

Community reviews

Related threats