VulnerabilityPublished 17 Sep 2026Updated 23 Sep 2026

CVE-2026-93075: Linux kernel · dax/fsdev: clear pgmap ops and owner on unbind

Affects Linux kernelSource GCVE Database

Authoritative record:CVE-2026-93075

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 is available that clears pgmap->ops and pgmap->owner on unbind to prevent stale handler usage. Users should apply the official kernel updates that include this patch. Since this is a kernel-level fix, upgrading to patched kernel versions is the recommended remediation.

Description

A vulnerability in the Linux kernel's dax/fsdev subsystem was resolved by ensuring that pgmap operations and ownership are cleared on unbind. Previously, stale handlers could remain on shared pgmap structures after unbinding static devices, potentially leading to use of freed memory handlers during memory failure events. This issue affects specific Linux kernel versions used in various Ubuntu LTS releases.

Impact

If exploited, this vulnerability could cause the kernel to execute stale or freed function pointers during memory failure handling, potentially leading to kernel instability or crashes. However, no known exploits are reported in the wild. The impact is limited to affected kernel versions and specific device configurations involving static dax devices.

Summary

The Linux kernel vulnerability (CVE-2026-93075) involves the dax/fsdev component where fsdev_dax_probe() sets pgmap->ops and pgmap->owner but does not clear them upon unbinding. For static devices, the shared pgmap retains stale fsdev_pagemap_ops after unbind, which can cause a subsequent memory_failure event to invoke stale or freed handlers. The fix registers a devm action to clear pgmap->ops and pgmap->owner on unbind, preventing the pgmap from carrying stale fsdev state once detached.

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