HIGH Introduced in 6.16
cpuset RemotePartition IsolationBypass
CVE-2026-98542
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H
01Description
In the Linux kernel, the following vulnerability has been resolved: cgroup/cpuset: Return PERR_NOCPUS in remote_partition_enable() on subpartitions_cpus conflict When a remote partition is created underneath an existing local partition via a non-partition (PRS_MEMBER) intermediate cgroup, update_prstate() sees parent->partition_root_state == PRS_MEMBER and calls remote_partition_enable(). Commit 86888c7bd117 ("cgroup/cpuset: Add warnings to catch inconsistency in exclusive CPUs") replaced the cpumask_intersects(tmp->new_cpus, subpartitions_cpus) error check in remote_partition_enable() with WARN_ON_ONCE(). As a result, remote_partition_enable() emits a warning and proceeds to enable the remote partition on CPUs that are already owned by the ancestor local partition in subpartitions_cpus. This can be reproduced on Linux 7.3.0-rc3 with: mkdir -p /tmp/cg1 mount -t cgroup2 none /tmp/cg1 echo "+cpuset" > /tmp/cg1/cgroup.subtree_control mkdir /tmp/cg1/A echo 1 > /tmp/cg1/A/cpuset.cpus echo 1 > /tmp/cg1/A/cpuset.cpus.exclusive echo root > /tmp/cg1/A/cpuset.cpus.partition echo "+cpuset" > /tmp/cg1/A/cgroup.subtree_control mkdir /tmp/cg1/A/B echo 1 > /tmp/cg1/A/B/cpuset.cpus echo 1 > /tmp/cg1/A/B/cpuset.cpus.exclusive echo "+cpuset" > /tmp/cg1/A/B/cgroup.subtree_control mkdir /tmp/cg1/A/B/D echo 1 > /tmp/cg1/A/B/D/cpuset.cpus echo 1 > /tmp/cg1/A/B/D/cpuset.cpus.exclusive echo root > /tmp/cg1/A/B/D/cpuset.cpus.partition which triggers: WARNING: kernel/cgroup/cpuset.c:1594 at remote_partition_enable+0x1c1/0x300 and leaves both /tmp/cg1/A and /tmp/cg1/A/B/D as active root partitions claiming exclusive CPU 1. Fix this by returning PERR_NOCPUS when tmp->new_cpus intersects subpartitions_cpus in remote_partition_enable(), matching the error code used by remote_cpus_update() for the same subpartitions_cpus conflict, and add a regression test case to tools/testing/selftests/cgroup/test_cpuset_prs.sh. Tested in QEMU on Linux 7.3.0-rc3 using the reproducer above and tools/testing/selftests/cgroup/test_cpuset_prs.sh.
02KernelScan AI Analysis
Risk summary
A logic error in the cpuset subsystem allows two partition roots to claim exclusive access to the same CPU, breaking CPU isolation guarantees. An attacker with local access and CAP_SYS_ADMIN (obtainable via unprivileged user namespaces on many systems) can trigger this by creating a specific cgroup hierarchy, leading to CPU contention, scheduler instability, and potential information leakage between workloads that should be isolated.
Vulnerability analysis
When a remote partition is created beneath an existing local partition with a non-partition intermediate cgroup, the kernel's remote_partition_enable() function fails to properly reject the operation if the requested CPUs overlap with CPUs already owned by an ancestor partition. A previous commit replaced the correct error check with a warning-only check, causing the kernel to emit a warning but proceed to enable the conflicting partition anyway. This leaves two active partitions claiming exclusive use of the same CPU, violating the isolation guarantees that cpuset partitions are designed to provide. The fix restores the proper error path, returning PERR_NOCPUS when a conflict with subpartitions_cpus is detected. The vulnerability is reachable by any local user who can mount a cgroup2 filesystem and configure cpuset controllers — typically requiring CAP_SYS_ADMIN, which unprivileged users can obtain through user namespaces on systems where unprivileged user namespace creation is permitted.
Lifecycle
03Fix Versions
| Branch | Introduced | Fixed in | Patch commit |
|---|---|---|---|
| 6.18 | 6.16 | 6.18.55 | 241e67b60308 |
| 7.2 | 6.16 | 7.2.9 | 0751ab665cb3 |
| mainline | 6.16 | 7.3 | 31c88350b7dd |