CVE-2022-49779

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

kprobes: Skip clearing aggrprobe's post_handler in kprobe-on-ftrace case

In __unregister_kprobe_top(), if the currently unregistered probe has post_handler but other child probes of the aggrprobe do not have post_handler, the post_handler of the aggrprobe is cleared. If this is a ftrace-based probe, there is a problem. In later calls to disarm_kprobe(), we will use kprobe_ftrace_ops because post_handler is NULL. But we're armed with kprobe_ipmodify_ops. This triggers a WARN in __disarm_kprobe_ftrace() and may even cause use-after-free:

Failed to disarm kprobe-ftrace at kernel_clone+0x0/0x3c0 (error -2) WARNING: CPU: 5 PID: 137 at kernel/kprobes.c:1135 __disarm_kprobe_ftrace.isra.21+0xcf/0xe0 Modules linked in: testKprobe_007(-) CPU: 5 PID: 137 Comm: rmmod Not tainted 6.1.0-rc4-dirty #18 [...] Call Trace: __disable_kprobe+0xcd/0xe0 __unregister_kprobe_top+0x12/0x150 ? mutex_lock+0xe/0x30 unregister_kprobes.part.23+0x31/0xa0 unregister_kprobe+0x32/0x40 __x64_sys_delete_module+0x15e/0x260 ? do_user_addr_fault+0x2cd/0x6b0 do_syscall_64+0x3a/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd [...]

For the kprobe-on-ftrace case, we keep the post_handler setting to identify this aggrprobe armed with kprobe_ipmodify_ops. This way we can disarm it correctly.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

May 1, 2025

Last Modified

November 7, 2025

References (5)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.4.225—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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 44× 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.

Showing the most recent 100 of 110 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2022-49779?
CVE-2022-49779 is a high vulnerability published on May 1, 2025. In the Linux kernel, the following vulnerability has been resolved: kprobes: Skip clearing aggrprobe's post_handler in kprobe-on-ftrace case In unregisterkprobetop(), if the currently unregistered probe has post_handler but other child probes of the aggrprobe do not have posthandler, the…
When was CVE-2022-49779 disclosed?
CVE-2022-49779 was first published in the National Vulnerability Database on May 1, 2025, with the most recent update on November 7, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-49779 actively exploited?
CVE-2022-49779 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.8% of all scored CVEs.
What is the CVSS score of CVE-2022-49779?
CVE-2022-49779 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-49779?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-49779, 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-49779

Explore →

Is Your Infrastructure Affected by CVE-2022-49779?

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

Start Free Scan →Browse All CVEs