VulnerabilityPublished 17 Sep 2026Updated 19 Oct 2026

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

Affects Linux kernelSource CVE Database V5

Not known to be exploited : upgrade to f48884ac31b6bfc99f36b3f207b8c0cbe5d54bd7 or 9b0f91dc9147a8601cec3d4d83cf13c6aaf71b27 when convenient.

Data as of 26 Oct 2026, 12:55 UTC

Severity

Unrated

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.
Patch: Available – fixed in f48884ac31b6bfc99f36b3f207b8c0cbe5d54bd7, 9b0f91dc9147a8601cec3d4d83cf13c6aaf71b27

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

Upgrade Linux kernel to f48884ac31b6bfc99f36b3f207b8c0cbe5d54bd7 or 9b0f91dc9147a8601cec3d4d83cf13c6aaf71b27.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ d5406bd458b0ac10b1301a4d5801d85c8f648637, < f48884ac31b6bfc99f36b3f207b8c0cbe5d54bd7	Fixed in f48884ac31b6bfc99f36b3f207b8c0cbe5d54bd7
LinuxLinux	Affected ≥ d5406bd458b0ac10b1301a4d5801d85c8f648637, < 9b0f91dc9147a8601cec3d4d83cf13c6aaf71b27	Fixed in 9b0f91dc9147a8601cec3d4d83cf13c6aaf71b27
LinuxLinux	Affected =7.1	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: dax/fsdev: clear pgmap ops and owner on unbind fsdev_dax_probe() sets pgmap->ops = &fsdev_pagemap_ops and pgmap->owner = dev_dax, but nothing ever clears them. For a dynamic device the pgmap is devm-allocated and freed on unbind, so this is harmless. For a static device the pgmap is the shared, long-lived one owned by the dax bus (kill_dev_dax() only NULLs dev_dax->pgmap for the non-static case), and device.c's probe sets only pgmap->type, never clearing ops/owner. So after fsdev unbinds a static device the stale fsdev_pagemap_ops survives on the shared pgmap. If the device is then rebound to device_dax (MEMORY_DEVICE_GENERIC, which installs no ->memory_failure), or the fsdev_dax module is unloaded, a subsequent memory_failure on that pgmap dispatches through the stale -- and possibly freed -- handler. Register a devm action that clears pgmap->ops and pgmap->owner on unbind, symmetric with setting them at probe, so the pgmap carries no fsdev state once fsdev is detached.

References

Community reviews

Loading reviews…