Vulnerability · Published Sep 17, 2026 · Assigned by Linux

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

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 10% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 90.4% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:14linux7.2.6-1DEBIAN-CVE-2026-93075
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-93075
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-93075
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-93075

Affected products (as reported)

VendorProductVersions
Linux Linux d5406bd458b0ac10b1301a4d5801d85c8f648637 – before 9b0f91dc9147a8601cec3d4d83cf13c6aaf71b27d5406bd458b0ac10b1301a4d5801d85c8f648637 – before f48884ac31b6bfc99f36b3f207b8c0cbe5d54bd7
Linux Linux 7.1

References