Skip to content
Fencer Vulns
medium 5.5

CVE-2023-52942 json

cgroup/cpuset: Fix wrong check in update_parent_subparts_cpumask()

published 2025-03-27 19 mo ago modified 2026-11-05 3 d ago also EUVD-2023-59748

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 13%
public exploits
0
none known

Summary

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

Patch / fix

  • Linux Linux 6.1.11, 6.2
  • linux Debian 14, Debian 13, Debian 12 6.1.11-1

debian advisories DEBIAN-CVE-2023-52942

  • kernel RHEL 9.2 EUS 5.14.0-284.48.1.el9_2
  • perf RHEL 9.2 EUS 5.14.0-284.48.1.el9_2
  • rtla RHEL 9.2 EUS 5.14.0-284.48.1.el9_2
  • bpftool RHEL 9.2 EUS 7.0.0-284.48.1.el9_2
  • kernel-64k RHEL 9.2 EUS 5.14.0-284.48.1.el9_2
  • kernel-core RHEL 9.2 EUS 5.14.0-284.48.1.el9_2
  • kernel-tools RHEL 9.2 EUS 5.14.0-284.48.1.el9_2
  • python3-perf RHEL 9.2 EUS 5.14.0-284.48.1.el9_2

red hat advisories RHSA-2024:0448

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-52942 updated cvss 4.1

kernel: cgroup/cpuset: Fix wrong check in update_parent_subparts_cpumask()

  • Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
    affected: no fix available “Fix deferred”
  • Red Hat CodeReady Linux Builder EUS (v.9.2) kernel-debuginfo-common-s390x 5.14.0-284.48.1.el9_2, kernel-debuginfo-common-x86_64 5.14.0-284.48.1.el9_2, kernel-debuginfo-common-aarch64 5.14.0-284.48.1.el9_2, kernel-debuginfo-common-ppc64le 5.14.0-284.48.1.el9_2 Red Hat Enterprise Linux AppStream EUS (v.9.2) perf 5.14.0-284.48.1.el9_2, rtla 5.14.0-284.48.1.el9_2, kernel-devel-matched 5.14.0-284.48.1.el9_2, kernel-64k-devel-matched 5.14.0-284.48.1.el9_2, kernel-debug-devel-matched 5.14.0-284.48.1.el9_2, kernel-debuginfo-common-s390x 5.14.0-284.48.1.el9_2, +5 more Red Hat Enterprise Linux BaseOS EUS (v.9.2) bpftool 7.0.0-284.48.1.el9_2, kernel 5.14.0-284.48.1.el9_2, kernel-64k 5.14.0-284.48.1.el9_2, kernel-core 5.14.0-284.48.1.el9_2, kernel-tools 5.14.0-284.48.1.el9_2, python3-perf 5.14.0-284.48.1.el9_2, +28 more
    fixed: vendor fix RHSA-2024:0448
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 10 kernel
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
3 d ago

Exploit prediction

0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Linux Linux

Classification

Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.