{"api_version":"1","generated_at":"2026-11-03T16:43:39+00:00","cve":"CVE-2026-98972","urls":{"html":"https://cve.report/CVE-2026-98972","api":"https://cve.report/api/cve/CVE-2026-98972.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-98972","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-98972"},"summary":{"title":"cgroup/cpuset: Don't access cpuset_cgrp_subsys.root in is_in_v2_mode()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncgroup/cpuset: Don't 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","state":"PUBLISHED","assigner":"Linux","published_at":"2026-10-23 13:17:18","updated_at":"2026-10-23 13:17:18"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/988bf67a13890a37a33201f95947095ca9bec856","name":"https://git.kernel.org/stable/c/988bf67a13890a37a33201f95947095ca9bec856","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/e06b678e3b4e12fdaa0b51a7a5a54abc5dbd6469","name":"https://git.kernel.org/stable/c/e06b678e3b4e12fdaa0b51a7a5a54abc5dbd6469","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-98972","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98972","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b8d1b8ee93df8ffbabbeadd65d39853cfad6d698 988bf67a13890a37a33201f95947095ca9bec856 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b8d1b8ee93df8ffbabbeadd65d39853cfad6d698 e06b678e3b4e12fdaa0b51a7a5a54abc5dbd6469 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4.14","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 4.14 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.11 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"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't 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't 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"},"nvd":{"publishedDate":"2026-10-23 13:17:18","lastModifiedDate":"2026-10-23 13:17:18","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"98972","Ordinal":"1","Title":"cgroup/cpuset: Don't access cpuset_cgrp_subsys.root in is_in_v2_","CVE":"CVE-2026-98972","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"98972","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ncgroup/cpuset: Don't 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","Type":"Description","Title":"cgroup/cpuset: Don't access cpuset_cgrp_subsys.root in is_in_v2_"}]}}}