{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98972 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-98972 is a vulnerability in Linux, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-98972 and fix it if it is affected.\n\nWhat it is: CVE-2026-98972 is a vulnerability in Linux, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-98972 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98972/ (Markdown: https://insights.sbomify.com/CVE-2026-98972/index.md)","id":"CVE-2026-98972","markdown":"https://insights.sbomify.com/CVE-2026-98972/index.md","name":"CVE-2026-98972","record":{"aliases":["AZL-110798","BELL-CVE-2026-98972","DEBIAN-CVE-2026-98972","GHSA-pv9v-q67q-mhqc","UBUNTU-CVE-2026-98972"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"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","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"cgroup/cpuset: Don't access cpuset_cgrp_subsys.root in is_in_v2_mode()","id":"CVE-2026-98972","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"drm/bridge: Fix unlocked list_del in drm_bridge_add()","id":"CVE-2026-98973"},"packages":[],"prev":{"headline":"gpio: exar: initialize the ID before registering its cleanup","id":"CVE-2026-98971"},"products":["Linux"],"published":"2026-10-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-23","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-98972/"}