VulnerabilityPublished 23 Oct 2026

CVE-2026-98972: Linux kernel · cgroup/cpuset: Don't access cpuset_cgrp_subsys.root in is_in_v2_mode()

Source GCVE Database

Authoritative record:CVE-2026-98972· High

Not known to be exploited : upgrade to e06b678e3b4e12fdaa0b51a7a5a54abc5dbd6469 or 988bf67a13890a37a33201f95947095ca9bec856 soon.

Data as of 26 Oct 2026, 12:55 UTC

Severity

High

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in e06b678e3b4e12fdaa0b51a7a5a54abc5dbd6469, 988bf67a13890a37a33201f95947095ca9bec856

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-pv9v-q67q-mhqc

What to do

Upgrade Linux kernel to e06b678e3b4e12fdaa0b51a7a5a54abc5dbd6469 or 988bf67a13890a37a33201f95947095ca9bec856.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ b8d1b8ee93df8ffbabbeadd65d39853cfad6d698, < e06b678e3b4e12fdaa0b51a7a5a54abc5dbd6469	Fixed in e06b678e3b4e12fdaa0b51a7a5a54abc5dbd6469
LinuxLinux	Affected ≥ b8d1b8ee93df8ffbabbeadd65d39853cfad6d698, < 988bf67a13890a37a33201f95947095ca9bec856	Fixed in 988bf67a13890a37a33201f95947095ca9bec856
LinuxLinux	Affected =4.14	Fixed in–

Description

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

References

Community reviews

Loading reviews…