Vulnerability-Lookup

GHSA-M6JW-VJQW-78FH

Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32

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

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-93075"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-17T17:18:01Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndax/fsdev: clear pgmap ops and owner on unbind\n\nfsdev_dax_probe() sets pgmap-\u003eops = \u0026fsdev_pagemap_ops and\npgmap-\u003eowner = dev_dax, but nothing ever clears them. For a dynamic\ndevice the pgmap is devm-allocated and freed on unbind, so this is\nharmless. For a static device the pgmap is the shared, long-lived one\nowned by the dax bus (kill_dev_dax() only NULLs dev_dax-\u003epgmap for the\nnon-static case), and device.c\u0027s probe sets only pgmap-\u003etype, never\nclearing ops/owner.\n\nSo after fsdev unbinds a static device the stale fsdev_pagemap_ops\nsurvives on the shared pgmap. If the device is then rebound to\ndevice_dax (MEMORY_DEVICE_GENERIC, which installs no -\u003ememory_failure),\nor the fsdev_dax module is unloaded, a subsequent memory_failure on that\npgmap dispatches through the stale -- and possibly freed -- handler.\n\nRegister a devm action that clears pgmap-\u003eops and pgmap-\u003eowner on unbind,\nsymmetric with setting them at probe, so the pgmap carries no fsdev state\nonce fsdev is detached.",
  "id": "GHSA-m6jw-vjqw-78fh",
  "modified": "2026-09-17T18:32:09Z",
  "published": "2026-09-17T18:32:09Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93075"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/9b0f91dc9147a8601cec3d4d83cf13c6aaf71b27"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/f48884ac31b6bfc99f36b3f207b8c0cbe5d54bd7"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-93075 (GCVE-0-2026-93075)

Vulnerability from cvelistv5 – Published: 2026-09-17 16:10 – Updated: 2026-09-17 16:10

Title

dax/fsdev: clear pgmap ops and owner on unbind

Summary

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.

Severity

No CVSS data available.

Assigner

Linux mitre root

References

2 references

URL	Tags
https://git.kernel.org/stable/c/9b0f91dc9147a8601…
https://git.kernel.org/stable/c/f48884ac31b6bfc99…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: d5406bd458b0ac10b1301a4d5801d85c8f648637 , < 9b0f91dc9147a8601cec3d4d83cf13c6aaf71b27 (git) Affected: d5406bd458b0ac10b1301a4d5801d85c8f648637 , < f48884ac31b6bfc99f36b3f207b8c0cbe5d54bd7 (git)
Linux	Linux	Affected: 7.1 Unaffected: 0 , < 7.1 (semver) Unaffected: 7.2.6 , ≤ 7.2.* (semver) Unaffected: 7.3-rc1 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/dax/fsdev.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "9b0f91dc9147a8601cec3d4d83cf13c6aaf71b27",
              "status": "affected",
              "version": "d5406bd458b0ac10b1301a4d5801d85c8f648637",
              "versionType": "git"
            },
            {
              "lessThan": "f48884ac31b6bfc99f36b3f207b8c0cbe5d54bd7",
              "status": "affected",
              "version": "d5406bd458b0ac10b1301a4d5801d85c8f648637",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/dax/fsdev.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "7.1"
            },
            {
              "lessThan": "7.1",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3-rc1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.6",
                  "versionStartIncluding": "7.1",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3-rc1",
                  "versionStartIncluding": "7.1",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndax/fsdev: clear pgmap ops and owner on unbind\n\nfsdev_dax_probe() sets pgmap-\u003eops = \u0026fsdev_pagemap_ops and\npgmap-\u003eowner = dev_dax, but nothing ever clears them. For a dynamic\ndevice the pgmap is devm-allocated and freed on unbind, so this is\nharmless. For a static device the pgmap is the shared, long-lived one\nowned by the dax bus (kill_dev_dax() only NULLs dev_dax-\u003epgmap for the\nnon-static case), and device.c\u0027s probe sets only pgmap-\u003etype, never\nclearing ops/owner.\n\nSo after fsdev unbinds a static device the stale fsdev_pagemap_ops\nsurvives on the shared pgmap. If the device is then rebound to\ndevice_dax (MEMORY_DEVICE_GENERIC, which installs no -\u003ememory_failure),\nor the fsdev_dax module is unloaded, a subsequent memory_failure on that\npgmap dispatches through the stale -- and possibly freed -- handler.\n\nRegister a devm action that clears pgmap-\u003eops and pgmap-\u003eowner on unbind,\nsymmetric with setting them at probe, so the pgmap carries no fsdev state\nonce fsdev is detached."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-17T16:10:57.699Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/9b0f91dc9147a8601cec3d4d83cf13c6aaf71b27"
        },
        {
          "url": "https://git.kernel.org/stable/c/f48884ac31b6bfc99f36b3f207b8c0cbe5d54bd7"
        }
      ],
      "title": "dax/fsdev: clear pgmap ops and owner on unbind",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-93075",
    "datePublished": "2026-09-17T16:10:57.699Z",
    "dateReserved": "2026-09-17T15:57:05.661Z",
    "dateUpdated": "2026-09-17T16:10:57.699Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.