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

CVE record · `CVE-2023-52942`

- **Identifiers:** `CVE-2023-52942`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 27 Mar 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 27 Mar 2025, 16:37 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `f0af1bfc27b52a4d42510051154c61bd176a8f06 to before a2ab7f2cf5ef8f0c6212a246e681d1fe358cec1f` (git)
  - affected: `f0af1bfc27b52a4d42510051154c61bd176a8f06 to before e5ae8803847b80fe9d744a3174abe2b7bfed222a` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.1`
  - unaffected: `before 6.1` (semver)
  - unaffected: `6.1.11 to 6.1.*, inclusive` (semver)
  - unaffected: `6.2 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel's cgroup/cpuset code has a wrong check in update_parent_subparts_cpumask() that can leave a parent cpuset with no effective CPUs while it still has tasks, which can cause a system panic. The source gives few details on what an attacker needs to trigger it. Upgrade to Linux kernel 6.1.11 or later in the 6.1 series, or to 6.2 or later.

Written 16 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0023, the 13th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 27 Mar 2025, 16:37 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2023-52942)
- 27 Mar 2025, 17:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2023-52942)

## Sources

- [CVE List: CVE-2023-52942](https://www.cve.org/CVERecord?id=CVE-2023-52942)
- [NVD: CVE-2023-52942](https://nvd.nist.gov/vuln/detail/CVE-2023-52942)

### References from the CNA

- <https://git.kernel.org/stable/c/a2ab7f2cf5ef8f0c6212a246e681d1fe358cec1f>
- <https://git.kernel.org/stable/c/e5ae8803847b80fe9d744a3174abe2b7bfed222a>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2023-52942>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2023-52942/>. Everything for agents: <https://agentprime.io/llms.txt>.
