CVE-2022-49647

cgroup: Use separate src/dst nodes when preloading css_sets for migration

HIGH
7.8
CVSS Score
Published: February 26, 2025 at 02:23 AM UTC
Updated: August 5, 2026 at 09:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: cgroup: Use separate src/dst nodes when preloading css_sets for migration Each cset (css_set) is pinned by its tasks. When we're moving tasks around across csets for a migration, we need to hold the source and destination csets to ensure that they don't go away while we're moving tasks about. This is done by linking cset->mg_preload_node on either the mgctx->preloaded_src_csets or mgctx->preloaded_dst_csets list. Using the same cset->mg_preload_node for both the src and dst lists was deemed okay as a cset can't be both the source and destination at the same time. Unfortunately, this overloading becomes problematic when multiple tasks are involved in a migration and some of them are identity noop migrations while others are actually moving across cgroups. For example, this can happen with the following sequence on cgroup1: #1> mkdir -p /sys/fs/cgroup/misc/a/b #2> echo $$ > /sys/fs/cgroup/misc/a/cgroup.procs #3> RUN_A_COMMAND_WHICH_CREATES_MULTIPLE_THREADS & #4> PID=$! #5> echo $PID > /sys/fs/cgroup/misc/a/b/tasks #6> echo $PID > /sys/fs/cgroup/misc/a/cgroup.procs the process including the group leader back into a. In this final migration, non-leader threads would be doing identity migration while the group leader is doing an actual one. After #3, let's say the whole process was in cset A, and that after #4, the leader moves to cset B. Then, during #6, the following happens: 1. cgroup_migrate_add_src() is called on B for the leader. 2. cgroup_migrate_add_src() is called on A for the other threads. 3. cgroup_migrate_prepare_dst() is called. It scans the src list. 4. It notices that B wants to migrate to A, so it tries to A to the dst list but realizes that its ->mg_preload_node is already busy. 5. and then it notices A wants to migrate to A as it's an identity migration, it culls it by list_del_init()'ing its ->mg_preload_node and putting references accordingly. 6. The rest of migration takes place with B on the src list but nothing on the dst list. This means that A isn't held while migration is in progress. If all tasks leave A before the migration finishes and the incoming task pins it, the cset will be destroyed leading to use-after-free. This is caused by overloading cset->mg_preload_node for both src and dst preload lists. We wanted to exclude the cset from the src list but ended up inadvertently excluding it from the dst list too. This patch fixes the issue by separating out cset->mg_preload_node into ->mg_src_preload_node and ->mg_dst_preload_node, so that the src and dst preloadings don't interfere with each other.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.16 ≤ v < 4.14.2893.16 ≤ v < 4.19.2533.16 ≤ v < 5.10.1323.16 ≤ v < 5.15.563.16 ≤ v < 5.18.133.16 ≤ v < 5.193.16 ≤ v < 5.4.2074.15 ≤ v < 4.19.2534.20 ≤ v < 5.4.2075.11 ≤ v < 5.15.565.16 ≤ v < 5.18.135.5 ≤ v < 5.10.1325.19 rc15.19 rc25.19 rc35.19 rc45.19 rc55.19 rc6f817de98513d060023be4fa1d061b29a6515273e
Vendor states this is fixed in 05f7658210d1d331e8dd4cb6e7bbbe3df5f5ac27 (fixed)
Vendor states this is fixed in 07fd5b6cdf3cc30bfde8fe0f644771688be04447 (fixed)
Vendor states this is fixed in 0e41774b564befa6d271e8d5086bf870d617a4e6 (fixed)
Vendor states this is fixed in 54aee4e5ce8c21555286a6333e46c1713880cf93 (fixed)
Vendor states this is fixed in 7657e3958535d101a24ab4400f9b8062b9107cc4 (fixed)
Vendor states this is fixed in ad44e05f3e016bdcb1ad25af35ade5b5f41ccd68 (fixed)
Vendor states this is fixed in cec2bbdcc14fbaa6b95ee15a7c423b05d97038be (fixed)
Vendor states this is fixed in 3.16 (unaffected)
Vendor states this is fixed in 4.14.289 (unaffected)
Vendor states this is fixed in 4.19.253 (unaffected)
Vendor states this is fixed in 5.10.132 (unaffected)
Vendor states this is fixed in 5.15.56 (unaffected)
Vendor states this is fixed in 5.18.13 (unaffected)
Vendor states this is fixed in 5.19 (unaffected)
Vendor states this is fixed in 5.4.207 (unaffected)

References (7)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/05f7658210d1d331e8dd4cb6e7bbbe3df5f5ac27
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/07fd5b6cdf3cc30bfde8fe0f644771688be04447
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/0e41774b564befa6d271e8d5086bf870d617a4e6
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/54aee4e5ce8c21555286a6333e46c1713880cf93
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/7657e3958535d101a24ab4400f9b8062b9107cc4
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/ad44e05f3e016bdcb1ad25af35ade5b5f41ccd68
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/cec2bbdcc14fbaa6b95ee15a7c423b05d97038be

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusANALYZED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card