Vulnerability-Lookup

GHSA-PV9V-Q67Q-MHQC

Vulnerability from github – Published: 2026-10-23 15:31 – Updated: 2026-10-23 15:31

Details

In the Linux kernel, the following vulnerability has been resolved:

cgroup/cpuset: Don't access cpuset_cgrp_subsys.root in is_in_v2_mode()

After seeing the patch [1] to guard is_in_v2_mode() with RCU, it makes me realize that is_in_v2_mode() may be called in a context where a new cgroup filesystem is being rebound with stale cpuset_cgrp_subsys.root pointer. Avoid this potential UaF situation by adding a new cpuset_v2_mode flag which is set when the cpuset_v2_mode mount option is used. This flag is written into only when cpuset_bind() is being called with a stable cpuset_cgrp_subsys.root value. The is_in_v2_mode() helper is modified to read the new cpuset_v2_mode flag instead of accessing cpuset_cgrp_subsys.root directly.

[1] https://lore.kernel.org/lkml/20260929084124.626693-2-arighi@nvidia.com

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-98972"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-10-23T13:17:18Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ncgroup/cpuset: Don\u0027t access cpuset_cgrp_subsys.root in is_in_v2_mode()\n\nAfter seeing the patch [1] to guard is_in_v2_mode() with RCU, it makes\nme realize that is_in_v2_mode() may be called in a context where a new\ncgroup filesystem is being rebound with stale cpuset_cgrp_subsys.root\npointer. Avoid this potential UaF situation by adding a new cpuset_v2_mode\nflag which is set when the cpuset_v2_mode mount option is used. This\nflag is written into only when cpuset_bind() is being called with a\nstable cpuset_cgrp_subsys.root value. The is_in_v2_mode() helper is\nmodified to read the new cpuset_v2_mode flag instead of accessing\ncpuset_cgrp_subsys.root directly.\n\n[1] https://lore.kernel.org/lkml/20260929084124.626693-2-arighi@nvidia.com",
  "id": "GHSA-pv9v-q67q-mhqc",
  "modified": "2026-10-23T15:31:33Z",
  "published": "2026-10-23T15:31:33Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98972"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/988bf67a13890a37a33201f95947095ca9bec856"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/e06b678e3b4e12fdaa0b51a7a5a54abc5dbd6469"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-98972 (GCVE-0-2026-98972)

Vulnerability from cvelistv5 – Published: 2026-10-23 12:19 – Updated: 2026-10-23 12:19

Title

cgroup/cpuset: Don't access cpuset_cgrp_subsys.root in is_in_v2_mode()

Summary

In the Linux kernel, the following vulnerability has been resolved: cgroup/cpuset: Don't access cpuset_cgrp_subsys.root in is_in_v2_mode() After seeing the patch [1] to guard is_in_v2_mode() with RCU, it makes me realize that is_in_v2_mode() may be called in a context where a new cgroup filesystem is being rebound with stale cpuset_cgrp_subsys.root pointer. Avoid this potential UaF situation by adding a new cpuset_v2_mode flag which is set when the cpuset_v2_mode mount option is used. This flag is written into only when cpuset_bind() is being called with a stable cpuset_cgrp_subsys.root value. The is_in_v2_mode() helper is modified to read the new cpuset_v2_mode flag instead of accessing cpuset_cgrp_subsys.root directly. [1] https://lore.kernel.org/lkml/20260929084124.626693-2-arighi@nvidia.com

Severity

No CVSS data available.

Assigner

Linux CNA under the mitre root

CNA scorecard D 53/100 over 7061 records in the last 180 days details

References

2 references

URL	Tags
https://git.kernel.org/stable/c/988bf67a13890a37a…
https://git.kernel.org/stable/c/e06b678e3b4e12fda…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: b8d1b8ee93df8ffbabbeadd65d39853cfad6d698 , < 988bf67a13890a37a33201f95947095ca9bec856 (git) Affected: b8d1b8ee93df8ffbabbeadd65d39853cfad6d698 , < e06b678e3b4e12fdaa0b51a7a5a54abc5dbd6469 (git)
Linux	Linux	Affected: 4.14 Unaffected: 0 , < 4.14 (semver) Unaffected: 7.2.11 , ≤ 7.2.* (semver) Unaffected: 7.3 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "kernel/cgroup/cpuset.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "988bf67a13890a37a33201f95947095ca9bec856",
              "status": "affected",
              "version": "b8d1b8ee93df8ffbabbeadd65d39853cfad6d698",
              "versionType": "git"
            },
            {
              "lessThan": "e06b678e3b4e12fdaa0b51a7a5a54abc5dbd6469",
              "status": "affected",
              "version": "b8d1b8ee93df8ffbabbeadd65d39853cfad6d698",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "kernel/cgroup/cpuset.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "4.14"
            },
            {
              "lessThan": "4.14",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.11",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.11",
                  "versionStartIncluding": "4.14",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3",
                  "versionStartIncluding": "4.14",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncgroup/cpuset: Don\u0027t access cpuset_cgrp_subsys.root in is_in_v2_mode()\n\nAfter seeing the patch [1] to guard is_in_v2_mode() with RCU, it makes\nme realize that is_in_v2_mode() may be called in a context where a new\ncgroup filesystem is being rebound with stale cpuset_cgrp_subsys.root\npointer. Avoid this potential UaF situation by adding a new cpuset_v2_mode\nflag which is set when the cpuset_v2_mode mount option is used. This\nflag is written into only when cpuset_bind() is being called with a\nstable cpuset_cgrp_subsys.root value. The is_in_v2_mode() helper is\nmodified to read the new cpuset_v2_mode flag instead of accessing\ncpuset_cgrp_subsys.root directly.\n\n[1] https://lore.kernel.org/lkml/20260929084124.626693-2-arighi@nvidia.com"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-23T12:19:45.458Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/988bf67a13890a37a33201f95947095ca9bec856"
        },
        {
          "url": "https://git.kernel.org/stable/c/e06b678e3b4e12fdaa0b51a7a5a54abc5dbd6469"
        }
      ],
      "title": "cgroup/cpuset: Don\u0027t access cpuset_cgrp_subsys.root in is_in_v2_mode()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-98972",
    "datePublished": "2026-10-23T12:19:45.458Z",
    "dateReserved": "2026-09-25T10:25:14.383Z",
    "dateUpdated": "2026-10-23T12:19:45.458Z",
    "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.

Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

Order JSON

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

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.

Action not permitted