CVE Catalog

CVE-2026-98972

Unknown
Published: Translated: NVD NIST

Summary

In the Linux kernel cgroup/cpuset subsystem, is_in_v2_mode() may be called in a context where a new cgroup filesystem is being rebound with a stale cpuset_cgrp_subsys.root pointer. To avoid a potential use-after-free, a new cpuset_v2_mode flag is set when the cpuset_v2_mode mount option is used and written only when cpuset_bind() runs with a stable cpuset_cgrp_subsys.root value. is_in_v2_mode() now reads this flag instead of accessing cpuset_cgrp_subsys.root directly.

Risk Assessment

A potential use-after-free in the kernel can lead to system crashes or, under favorable conditions, privilege escalation. The risk applies to systems using cgroups v2 with the cpuset controller.

Recommendation

Update the Linux kernel to a version with the fix introducing the cpuset_v2_mode flag. Until patched, avoid frequent remounting of the cgroup filesystem with the cpuset_v2_mode option.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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/[email protected]

Vulnerability data from NVD (NIST) · CISA KEV · EPSS