{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  dax/fsdev: clear pgmap ops and owner on unbind  fsdev_dax_probe() sets pgmap-\u003eops = \u0026fsdev_pagemap_ops and pgmap-\u003eowner = 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-\u003epgmap for the non-static case), and device.c's probe sets only pgmap-\u003etype, 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 -\u003ememory_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-\u003eops and pgmap-\u003eowner on unbind, symmetric with setting them at probe, so the pgmap carries no fsdev state once fsdev is detached.",
  "id": "DEBIAN-CVE-2026-93075",
  "modified": "2026-09-18T04:47:35.070574922Z",
  "published": "2026-09-17T17:18:01.440Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-93075"
    }
  ],
  "upstream": [
    "CVE-2026-93075"
  ]
}