The Linux kernel’s cpuset cgroup subsystem mis‑detects a conflict when a remote partition is enabled under an existing local partition. A change that replaced an error check with a warning allowed the remote partition to claim CPUs already owned by the ancestor partition, resulting in two active root partitions possessing the same exclusive CPU. This breach of cpuset isolation can lead to scheduling instability or a denial of service if critical processes run on the conflicted CPUs.

All Linux kernels that have not yet included the fix for this issue are affected. This includes kernel 7.3.0‑rc3 and earlier builds lacking the commit that restores proper conflict testing. No specific vendor patch is listed; the vulnerability applies broadly to any unpatched kernel configuration that supports cgroup cpuset partitioning.

The vulnerability requires local access with permission to manipulate the cgroup filesystem; it does not provide remote entry or privilege escalation. Exploitation is demonstrated by creating nested cpuset partitions as shown in the reproduction steps. With a CVSS score of 2.3 and an EPSS score of <1%, the likelihood of exploitation is low. The flaw is not listed in the CISA KEV catalog, but systems that rely on strict CPU isolation may still experience service disruption when the conflict is triggered.