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
Published: 2026-10-23
Score: 4.1 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Use‑After‑Free potentially leading to kernel crash or privilege escalation
Action: Patch
AI Analysis

Impact

The Linux kernel’s cgroup cpuset subsystem contains a Use‑After‑Free flaw. The helper function is_in_v2_mode() may read a stale cpuset_cgrp_subsys.root pointer when the cpuset filesystem is rebound, which could trigger a kernel fault. Because the pointer is used by privileged kernel code, an attacker who can cause the stale read might execute code at kernel level, leading to a kernel crash or privilege escalation. The patch resolves the issue by adding a cpuset_v2_mode flag that is written only after a stable cpuset bind and by changing is_in_v2_mode() to read that flag instead of the potentially stale root pointer. This is an instance of CWE-825 weakness.

Affected Systems

The flaw affects all kernel builds that include the cgroup cpuset subsystem and have not incorporated the commit that replaces the unsafe root pointer with the cpuset_v2_mode flag. Because no specific version list is supplied, any kernel that has not applied the patch and that mounts the cgroup cpuset filesystem is potentially vulnerable. Users of recent stable kernels that have not yet received the fix should verify against commit 988bf67a13890a37a33201f95947095ca9bec856.

Risk and Exploitability

The CVSS score is 4.1, indicating low severity, while the EPSS score is <1%, demonstrating a low probability of exploitation in the wild. The vulnerability is not listed in the CISA KEV catalog. The likely attack vector is local or privileged, requiring an attacker to trigger a stale read by rebinding the cpuset filesystem, which could result in a crash or local privilege escalation. No public exploits have been reported, but the kernel‑level nature of the defect warrants prompt attention.

Generated by OpenCVE AI on October 29, 2026 at 21:55 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the kernel to a version that includes the commit adding the cpuset_v2_mode flag and guarding the stale root pointer access
  • Reboot the system so the updated kernel initializes the cpuset subsystem with the new flag
  • If a kernel upgrade cannot be performed immediately, temporarily disable the cpuset subsystem or unmount the cgroup cpuset v2 filesystem until the patch is applied

Generated by OpenCVE AI on October 29, 2026 at 21:55 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 29 Oct 2026 20:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-665

Thu, 29 Oct 2026 12:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-825
References
Metrics threat_severity

None

cvssV3_1

{'score': 4.1, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate


Fri, 23 Oct 2026 18:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-665

Fri, 23 Oct 2026 17:45:00 +0000

Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux

Fri, 23 Oct 2026 12:45:00 +0000

Type Values Removed Values Added
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
Title cgroup/cpuset: Don't access cpuset_cgrp_subsys.root in is_in_v2_mode()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-23T12:19:45.458Z

Reserved: 2026-09-25T10:25:14.383Z

Link: CVE-2026-98972

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-23T13:17:18.783

Modified: 2026-10-23T13:17:18.783

Link: CVE-2026-98972

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-10-23T00:00:00Z

Links: CVE-2026-98972 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-29T22:00:09Z

Weaknesses
  • CWE-825

    Expired Pointer Dereference