CVE-2022-49970

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2025-06-18. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2022-55250 (ENISA EUVD) · GHSA-4rx8-g9mx-575c (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

bpf, cgroup: Fix kernel BUG in purge_effective_progs

Syzkaller reported a triggered kernel BUG as follows:

------------[ cut here ]------------ kernel BUG at kernel/bpf/cgroup.c:925! invalid opcode: 0000 [#1] PREEMPT SMP NOPTI CPU: 1 PID: 194 Comm: detach Not tainted 5.19.0-14184-g69dac8e431af #8 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:__cgroup_bpf_detach+0x1f2/0x2a0 Code: 00 e8 92 60 30 00 84 c0 75 d8 4c 89 e0 31 f6 85 f6 74 19 42 f6 84 28 48 05 00 00 02 75 0e 48 8b 80 c0 00 00 00 48 85 c0 75 e5 <0f> 0b 48 8b 0c5 RSP: 0018:ffffc9000055bdb0 EFLAGS: 00000246 RAX: 0000000000000000 RBX: ffff888100ec0800 RCX: ffffc900000f1000 RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff888100ec4578 RBP: 0000000000000000 R08: ffff888100ec0800 R09: 0000000000000040 R10: 0000000000000000 R11: 0000000000000000 R12: ffff888100ec4000 R13: 000000000000000d R14: ffffc90000199000 R15: ffff888100effb00 FS: 00007f68213d2b80(0000) GS:ffff88813bc80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000055f74a0e5850 CR3: 0000000102836000 CR4: 00000000000006e0 Call Trace: cgroup_bpf_prog_detach+0xcc/0x100 __sys_bpf+0x2273/0x2a00 __x64_sys_bpf+0x17/0x20 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f68214dbcb9 Code: 08 44 89 e0 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff8 RSP: 002b:00007ffeb487db68 EFLAGS: 00000246 ORIG_RAX: 0000000000000141 RAX: ffffffffffffffda RBX: 000000000000000b RCX: 00007f68214dbcb9 RDX: 0000000000000090 RSI: 00007ffeb487db70 RDI: 0000000000000009 RBP: 0000000000000003 R08: 0000000000000012 R09: 0000000b00000003 R10: 00007ffeb487db70 R11: 0000000000000246 R12: 00007ffeb487dc20 R13: 0000000000000004 R14: 0000000000000001 R15: 000055f74a1011b0 Modules linked in: ---[ end trace 0000000000000000 ]---

Repetition steps:

For the following cgroup tree,

root | cg1 | cg2

  • attach prog2 to cg2, and then attach prog1 to cg1, both bpf progs
attach type is NONE or OVERRIDE.
  • write 1 to /proc/thread-self/fail-nth for failslab.
  • detach prog1 for cg1, and then kernel BUG occur.

Failslab injection will cause kmalloc fail and fall back to purge_effective_progs. The problem is that cg2 have attached another prog, so when go through cg2 layer, iteration will add pos to 1, and subsequent operations will be skipped by the following condition, and cg will meet NULL in the end.

if (pos && !(cg->bpf.flags[atype] & BPF_F_ALLOW_MULTI))

The NULL cg means no link or prog match, this is as expected, and it's not a bug. So here just skip the no match situation.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
22nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 18, 2025

Last Modified

November 5, 2026

Advisory Details (4)

Auto-updated Nov 13, 2026
Patch available.
Web page

bpf, cgroup: Fix kernel BUG in purge_effective_progs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c5f975e3ebfa57be13393c585a4b58ea707023cb
Web page

bpf, cgroup: Fix kernel BUG in purge_effective_progs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a1a05d3ae58299b040da4d5b27e72e81c2132e0b
Web page

bpf, cgroup: Fix kernel BUG in purge_effective_progs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7d6620f107bae6ed687ff07668e8e8f855487aa9
Web page

bpf, cgroup: Fix kernel BUG in purge_effective_progs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/222bd95c89b135fde21f0bd0cb5cc1611c0c576c

Vendor Advisories for CVE-2022-49970(1)

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 / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-284.11.1.el9_22023-05-09redhat
linuxKernel @ 5.10.142 (fixes >=5.10.138)—osv

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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (19 versions)
  • every version up to 5.10.148-1: fixed in 5.10.148-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.2-1: fixed in 6.0.2-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.2-1: fixed in 6.0.2-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.2-1: fixed in 6.0.2-1
—

Data Freshness Timeline

(refreshed 10× in last 7d / 42× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 219 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 119 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-14 16:56 UTCOSV refresh
  2. 2026-11-14 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  3. 2026-11-13 16:43 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  4. 2026-11-13 00:46 UTCEchelonGraph re-scored
  5. 2026-11-13 00:46 UTCVendor advisory
  6. 2026-11-13 00:46 UTCGHSA enrichmentGHSA-4rx8-g9mx-575c · GitHub severity HIGH · GitHub CVSS 7.1
  7. 2026-11-12 16:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  8. 2026-11-11 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  9. 2026-11-10 16:36 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  10. 2026-11-09 16:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  11. 2026-11-08 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  12. 2026-11-07 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  13. 2026-11-06 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  14. 2026-11-05 20:27 UTCVendor advisory
  15. 2026-11-05 20:27 UTCGHSA enrichmentGHSA-4rx8-g9mx-575c · GitHub severity HIGH · GitHub CVSS 7.1
  16. 2026-11-05 20:03 UTCEchelonGraph re-scored
  17. 2026-11-05 20:03 UTCVendor advisory
  18. 2026-11-05 20:03 UTCGHSA enrichmentGHSA-4rx8-g9mx-575c · GitHub severity HIGH · GitHub CVSS 7.1
  19. 2026-11-05 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  20. 2026-11-04 22:38 UTCEchelonGraph re-scored
  21. 2026-11-04 22:38 UTCVendor advisory
  22. 2026-11-04 22:38 UTCGHSA enrichmentGHSA-4rx8-g9mx-575c · GitHub severity HIGH · GitHub CVSS 7.1
  23. 2026-11-04 16:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  24. 2026-11-03 16:40 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  25. 2026-11-02 16:39 UTCEPSS rescoreEPSS 0.3% · 20th percentile
Show 75 more
  1. 2026-11-01 16:30 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-10-31 16:29 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  3. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  4. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  5. 2026-10-28 17:48 UTCEchelonGraph re-scored
  6. 2026-10-28 17:48 UTCGHSA enrichmentGHSA-4rx8-g9mx-575c · GitHub severity HIGH · GitHub CVSS 7.1
  7. 2026-10-28 16:28 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  8. 2026-10-27 16:28 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  9. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  10. 2026-10-25 17:54 UTCEchelonGraph re-scored
  11. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  12. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-10-22 16:30 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  15. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  16. 2026-10-21 05:35 UTCEchelonGraph re-scored
  17. 2026-10-21 05:35 UTCVendor advisory
  18. 2026-10-21 05:35 UTCGHSA enrichmentGHSA-4rx8-g9mx-575c · GitHub severity HIGH · GitHub CVSS 7.1
  19. 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  20. 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  21. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  22. 2026-10-18 08:19 UTCEchelonGraph re-scored
  23. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  24. 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  25. 2026-10-15 16:28 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  26. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  27. 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  28. 2026-10-12 18:41 UTCEchelonGraph re-scored
  29. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  30. 2026-10-11 22:04 UTCEchelonGraph re-scored
  31. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  32. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  33. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  34. 2026-10-08 17:05 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  35. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  36. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  37. 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  38. 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  39. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  40. 2026-10-02 11:10 UTCOSV refresh
  41. 2026-09-30 16:12 UTCEchelonGraph re-scored
  42. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  43. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  44. 2026-09-26 15:55 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  45. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  46. 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  47. 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  48. 2026-09-20 20:13 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  49. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  50. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  51. 2026-09-15 03:07 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  52. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  53. 2026-09-13 08:54 UTCOSV refresh
  54. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  55. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  56. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  57. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  58. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  59. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  60. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  61. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  62. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  63. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  64. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  65. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  66. 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  67. 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  68. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  69. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  70. 2026-08-25 10:11 UTCOSV refresh
  71. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  72. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  73. 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  74. 2026-08-18 13:45 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  75. 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.2% · 14th percentile

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2022-49970?
CVE-2022-49970 is a high-severity vulnerability; its CVE record was published on June 18, 2025. In the Linux kernel, the following vulnerability has been resolved: bpf, cgroup: Fix kernel BUG in purge_effective_progs Syzkaller reported a triggered kernel BUG as follows: ------------[ cut here ]------------ kernel BUG at kernel/bpf/cgroup.c:925! invalid opcode: 0000 [#1] PREEMPT SMP NOPTI CPU:…
When was the CVE record for CVE-2022-49970 published?
The CVE record for CVE-2022-49970 was published on June 18, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 5, 2026; the record at its source may have been updated since.
Is CVE-2022-49970 actively exploited?
CVE-2022-49970 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49970?
CVE-2022-49970 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2022-49970?
A fix for CVE-2022-49970 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-49970 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-49970

Explore →

Is Your Infrastructure Affected by CVE-2022-49970?

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

Book a Demo →Browse All CVEs