VDB

CVE-2025-39953

CVE-2025-39953 PUBLISHED

cgroup: split cgroup_destroy_wq into 3 workqueues

Reported by linux · Published October 4, 2025

In the Linux kernel, the following vulnerability has been resolved: cgroup: split cgroup_destroy_wq into 3 workqueues A hung task can occur during [1] LTP cgroup testing when repeatedly mounting/unmounting perf_event and net_prio controllers with systemd.unified_cgroup_hierarchy=1. The hang manifests in cgroup_lock_and_drain_offline() during root destruction. Related case: cgroup_fj_function_perf_event cgroup_fj_function.sh perf_event cgroup_fj_function_net_prio cgroup_fj_function.sh net_prio Call Trace: cgroup_lock_and_drain_offline+0x14c/0x1e8 cgroup_destroy_root+0x3c/0x2c0 css_free_rwork_fn+0x248/0x338 process_one_work+0x16c/0x3b8 worker_thread+0x22c/0x3b0 kthread+0xec/0x100 ret_from_fork+0x10/0x20 Root Cause: CPU0 CPU1 mount perf_event umount net_prio cgroup1_get_tree cgroup_kill_sb rebind_subsystems // root destruction enqueues // cgroup_destroy_wq // kill all perf_event css // one perf_event css A is dying // css A offline enqueues cgroup_destroy_wq // root destruction will be executed first css_free_rwork_fn cgroup_destroy_root cgroup_lock_and_drain_offline // some perf descendants are dying // cgroup_destroy_wq max_active = 1 // waiting for css A to die Problem scenario: 1. CPU0 mounts perf_event (rebind_subsystems) 2. CPU1 unmounts net_prio (cgroup_kill_sb), queuing root destruction work 3. A dying perf_event CSS gets queued for offline after root destruction 4. Root destruction waits for offline completion, but offline work is blocked behind root destruction in cgroup_destroy_wq (max_active=1) Solution: Split cgroup_destroy_wq into three dedicated workqueues: cgroup_offline_wq – Handles CSS offline operations cgroup_release_wq – Manages resource release cgroup_free_wq – Performs final memory deallocation This separation eliminates blocking in the CSS free path while waiting for offline operations to complete. [1] https://github.com/linux-test-project/ltp/blob/master/runtest/controllers

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
kernel-libbpf-develAmazon Linux1:6.1.155-176.282.amzn2023
kernel-tools-develAmazon Linux1:6.1.155-176.282.amzn2023
kernel-develAmazon Linux1:6.1.155-176.282.amzn2023
kernel-modules-extra-commonAmazon Linux1:6.1.155-176.282.amzn2023
kernel-headersAmazon Linux1:6.1.155-176.282.amzn2023
kernel-modules-extraAmazon Linux1:6.1.155-176.282.amzn2023
python3-perfAmazon Linux1:6.1.155-176.282.amzn2023
bpftoolAmazon Linux1:6.1.155-176.282.amzn2023
kernel6.12-modules-extra-commonAmazon Linux1:6.12.53-69.119.amzn2023
python3-perf6.12Amazon Linux1:6.12.53-69.119.amzn2023
kernelAmazon Linux1:6.1.155-176.282.amzn2023
kernel-toolsAmazon Linux1:6.1.155-176.282.amzn2023

5 more packages have a fixed version. See every fix in Lookup.

Affected products

VendorProductVersions
LinuxLinux334c3679ec4b2b113c35ebe37d2018b112dd5013, 334c3679ec4b2b113c35ebe37d2018b112dd5013, 334c3679ec4b2b113c35ebe37d2018b112dd5013
LinuxLinux4.6, 0, 5.4.300
amazon:2023kernel-libbpf-devel0
amazon:2023kernel-tools-devel0
amazon:2023kernel-devel0
amazon:2023kernel-modules-extra-common0
amazon:2023kernel-headers0
amazon:2023kernel-modules-extra0
amazon:2023python3-perf0
amazon:2023bpftool0
amazon:2023kernel6.12-modules-extra-common0
amazon:2023python3-perf6.120
amazon:2023kernel0
SiemensSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP3.1.6, 3.1.7
SiemensSIPLUS S7-1500 CPU 1518-4 PN/DP MFP3.1.6, 3.1.7
SiemensSIMATIC S7-1500 CPU 1518-4 PN/DP MFP3.1.7, 3.1.6
amazon:2023kernel-tools0
amazon:2023bpftool6.120
amazon:2023kernel-livepatch-6.1.155-176.2820
amazon:2023kernel-livepatch-6.12.53-69.1190

…and 15 more

Timeline

  • Oct 4, 2025 EPSS Score (30 in total, the first dated here)
  • Oct 4, 2025 CVE Published
  • Oct 6, 2025 Coalition ESS Score (7 in total, the first dated here)
  • Dec 15, 2025 Security Advisory (234 in total, the first dated here)
  • Mar 29, 2026 Distribution Patch (149 in total, the first dated here)

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-39953
vulnetix vdb fixes CVE-2025-39953

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-39953/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›