cgroup/cpuset: Fix wrong check in update_parent_subparts_cpumask()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
cgroup/cpuset: Fix wrong check in update_parent_subparts_cpumask()
It was found that the check to see if a partition could use up all the cpus from the parent cpuset in update_parent_subparts_cpumask() was incorrect. As a result, it is possible to leave parent with no effective cpu left even if there are tasks in the parent cpuset. This can lead to system panic as reported in [1].
Fix this probem by updating the check to fail the enabling the partition if parent's effective_cpus is a subset of the child's cpus_allowed.
Also record the error code when an error happens in update_prstate() and add a test case where parent partition and child have the same cpu list and parent has task. Enabling partition in the child will fail in this case.
[1] https://www.spinics.net/lists/cgroups/msg36254.html
From the CVE record · Linux
An incorrect check in the Linux kernel’s cgroup/cpuset code can leave a parent cpuset with no effective CPUs while it still has tasks, potentially causing a system panic. This can occur when a child partition is enabled with the same CPU list as its parent; the input does not specify the access needed to do so.
Operators running Linux kernels with the affected cgroup/cpuset code should check their kernel vendor’s guidance; affected versions are not specified.