CVE-2022-49647

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-02-27. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

A fix is available — apply it.

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:

  • cgroup_migrate_add_src() is called on B for the leader.
  • cgroup_migrate_add_src() is called on A for the other threads.
  • cgroup_migrate_prepare_dst() is called. It scans the src list.
  • 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.
  • 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.
  • 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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
20.3%
KEV
Not listed

Published

February 26, 2025

Last Modified

March 24, 2025

Vendor Advisories for CVE-2022-49647(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-513.5.1.el8_92023-11-14redhat
redhatkernel-0:5.14.0-284.11.1.el9_22023-05-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 02:16 UTCEG score recompute
  2. 2026-07-22 23:04 UTCEG score recompute
  3. 2026-07-22 14:06 UTCEPSS rescore
  4. 2026-07-22 14:06 UTCEPSS rescore
  5. 2026-07-20 17:05 UTCEPSS rescore
  6. 2026-07-19 14:29 UTCEPSS rescore
  7. 2026-07-19 14:29 UTCEPSS rescore
  8. 2026-07-19 02:27 UTCEPSS rescore
  9. 2026-07-19 02:27 UTCEPSS rescore
  10. 2026-07-18 10:03 UTCEPSS rescore
  11. 2026-07-18 10:03 UTCEPSS rescore
  12. 2026-07-16 17:00 UTCEPSS rescore
  13. 2026-07-15 16:56 UTCEPSS rescore
  14. 2026-07-15 16:56 UTCEPSS rescore
  15. 2026-07-15 01:58 UTCEPSS rescore
  16. 2026-07-15 01:58 UTCEPSS rescore
  17. 2026-07-13 22:28 UTCEPSS rescore
  18. 2026-07-13 22:28 UTCEPSS rescore
  19. 2026-07-13 06:11 UTCEPSS rescore
  20. 2026-07-13 06:11 UTCEPSS rescore
  21. 2026-07-12 05:44 UTCEPSS rescore
  22. 2026-07-11 08:25 UTCEPSS rescore
  23. 2026-07-11 08:25 UTCEPSS rescore
  24. 2026-07-09 19:08 UTCEPSS rescore
  25. 2026-07-07 13:44 UTCEPSS rescore
Show 67 more
  1. 2026-07-07 09:21 UTCOSV refresh
  2. 2026-07-06 16:25 UTCEPSS rescore
  3. 2026-07-06 02:21 UTCEPSS rescore
  4. 2026-07-05 02:28 UTCEPSS rescore
  5. 2026-07-04 06:29 UTCEPSS rescore
  6. 2026-07-01 15:04 UTCEPSS rescore
  7. 2026-06-30 23:21 UTCEPSS rescore
  8. 2026-06-30 23:20 UTCEPSS rescore
  9. 2026-06-29 14:04 UTCEPSS rescore
  10. 2026-06-28 14:06 UTCEPSS rescore
  11. 2026-06-28 04:54 UTCEPSS rescore
  12. 2026-06-28 04:54 UTCEPSS rescore
  13. 2026-06-27 03:07 UTCEPSS rescore
  14. 2026-06-27 03:07 UTCEPSS rescore
  15. 2026-06-25 13:48 UTCEPSS rescore
  16. 2026-06-25 13:48 UTCEPSS rescore
  17. 2026-06-24 14:03 UTCEPSS rescore
  18. 2026-06-24 14:03 UTCEPSS rescore
  19. 2026-06-23 21:31 UTCEPSS rescore
  20. 2026-06-23 21:31 UTCEPSS rescore
  21. 2026-06-22 14:24 UTCEPSS rescore
  22. 2026-06-21 14:55 UTCEPSS rescore
  23. 2026-06-21 14:55 UTCEPSS rescore
  24. 2026-06-21 01:58 UTCEPSS rescore
  25. 2026-06-21 01:58 UTCEPSS rescore
  26. 2026-06-19 19:24 UTCEPSS rescore
  27. 2026-06-19 19:24 UTCEPSS rescore
  28. 2026-06-18 20:35 UTCOSV refresh
  29. 2026-06-18 17:51 UTCEPSS rescore
  30. 2026-06-18 17:51 UTCEPSS rescore
  31. 2026-06-17 17:51 UTCEPSS rescore
  32. 2026-06-17 17:51 UTCEPSS rescore
  33. 2026-06-16 17:51 UTCEPSS rescore
  34. 2026-06-16 17:51 UTCEPSS rescore
  35. 2026-06-15 17:47 UTCEPSS rescore
  36. 2026-06-14 23:16 UTCEPSS rescore
  37. 2026-06-13 22:59 UTCEPSS rescore
  38. 2026-06-12 23:10 UTCEPSS rescore
  39. 2026-06-12 23:10 UTCEPSS rescore
  40. 2026-06-11 13:58 UTCEPSS rescore
  41. 2026-06-11 13:58 UTCEPSS rescore
  42. 2026-06-10 13:21 UTCEPSS rescore
  43. 2026-06-10 13:21 UTCEPSS rescore
  44. 2026-06-08 14:15 UTCEPSS rescore
  45. 2026-06-08 14:15 UTCEPSS rescore
  46. 2026-06-07 15:23 UTCEPSS rescore
  47. 2026-06-07 15:23 UTCEPSS rescore
  48. 2026-06-06 13:46 UTCEPSS rescore
  49. 2026-06-06 13:46 UTCEPSS rescore
  50. 2026-06-05 22:46 UTCEPSS rescore
  51. 2026-06-05 22:46 UTCEPSS rescore
  52. 2026-06-05 06:09 UTCEPSS rescore
  53. 2026-06-05 06:09 UTCEPSS rescore
  54. 2026-06-04 13:11 UTCEPSS rescore
  55. 2026-06-02 20:12 UTCEPSS rescore
  56. 2026-06-02 20:12 UTCEPSS rescore
  57. 2026-06-01 13:50 UTCEPSS rescore
  58. 2026-06-01 13:50 UTCEPSS rescore
  59. 2026-05-31 22:29 UTCEPSS rescore
  60. 2026-05-31 22:29 UTCEPSS rescore
  61. 2026-05-31 00:15 UTCEPSS rescore
  62. 2026-05-31 00:15 UTCEPSS rescore
  63. 2026-05-30 10:44 UTCEG score recompute
  64. 2026-05-30 10:44 UTCVendor advisory
  65. 2026-05-30 10:44 UTCGHSA enrichment
  66. 2026-05-29 13:43 UTCEPSS rescore
  67. 2026-05-29 13:35 UTCOSV refresh

Frequently asked(5)

What is CVE-2022-49647?
CVE-2022-49647 is a high vulnerability published on February 26, 2025. 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…
When was CVE-2022-49647 disclosed?
CVE-2022-49647 was first published in the National Vulnerability Database on February 26, 2025, with the most recent update on March 24, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-49647 actively exploited?
CVE-2022-49647 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-49647?
CVE-2022-49647 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-49647?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-49647, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-49647

Explore →

Is Your Infrastructure Affected by CVE-2022-49647?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.