CVE-2022-49977

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-06-18. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

A fix is available — apply it.

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

ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead

ftrace_startup does not remove ops from ftrace_ops_list when ftrace_startup_enable fails:

register_ftrace_function ftrace_startup __register_ftrace_function ... add_ftrace_ops(&ftrace_ops_list, ops) ... ... ftrace_startup_enable // if ftrace failed to modify, ftrace_disabled is set to 1 ... return 0 // ops is in the ftrace_ops_list.

When ftrace_disabled = 1, unregister_ftrace_function simply returns without doing anything: unregister_ftrace_function ftrace_shutdown if (unlikely(ftrace_disabled)) return -ENODEV; // return here, __unregister_ftrace_function is not executed, // as a result, ops is still in the ftrace_ops_list __unregister_ftrace_function ...

If ops is dynamically allocated, it will be free later, in this case, is_ftrace_trampoline accesses NULL pointer:

is_ftrace_trampoline ftrace_ops_trampoline do_for_each_ftrace_op(op, ftrace_ops_list) // OOPS! op may be NULL!

Syzkaller reports as follows: [ 1203.506103] BUG: kernel NULL pointer dereference, address: 000000000000010b [ 1203.508039] #PF: supervisor read access in kernel mode [ 1203.508798] #PF: error_code(0x0000) - not-present page [ 1203.509558] PGD 800000011660b067 P4D 800000011660b067 PUD 130fb8067 PMD 0 [ 1203.510560] Oops: 0000 [#1] SMP KASAN PTI [ 1203.511189] CPU: 6 PID: 29532 Comm: syz-executor.2 Tainted: G B W 5.10.0 #8 [ 1203.512324] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 [ 1203.513895] RIP: 0010:is_ftrace_trampoline+0x26/0xb0 [ 1203.514644] Code: ff eb d3 90 41 55 41 54 49 89 fc 55 53 e8 f2 00 fd ff 48 8b 1d 3b 35 5d 03 e8 e6 00 fd ff 48 8d bb 90 00 00 00 e8 2a 81 26 00 <48> 8b ab 90 00 00 00 48 85 ed 74 1d e8 c9 00 fd ff 48 8d bb 98 00 [ 1203.518838] RSP: 0018:ffffc900012cf960 EFLAGS: 00010246 [ 1203.520092] RAX: 0000000000000000 RBX: 000000000000007b RCX: ffffffff8a331866 [ 1203.521469] RDX: 0000000000000000 RSI: 0000000000000008 RDI: 000000000000010b [ 1203.522583] RBP: 0000000000000000 R08: 0000000000000000 R09: ffffffff8df18b07 [ 1203.523550] R10: fffffbfff1be3160 R11: 0000000000000001 R12: 0000000000478399 [ 1203.524596] R13: 0000000000000000 R14: ffff888145088000 R15: 0000000000000008 [ 1203.525634] FS: 00007f429f5f4700(0000) GS:ffff8881daf00000(0000) knlGS:0000000000000000 [ 1203.526801] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1203.527626] CR2: 000000000000010b CR3: 0000000170e1e001 CR4: 00000000003706e0 [ 1203.528611] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 1203.529605] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400

Therefore, when ftrace_startup_enable fails, we need to rollback registration process and remove ops from ftrace_ops_list.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
11.1%
KEV
Not listed

Published

June 18, 2025

Last Modified

November 14, 2025

References (8)

Vendor Advisories for CVE-2022-49977(11)

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

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-305.170.1.el8_42025-09-02redhat
redhatkernel-rt-0:5.14.0-284.134.1.rt14.419.el9_22025-08-27redhat
redhatkernel-0:4.18.0-372.158.1.el8_62025-08-27redhat
redhatkernel-rt-0:5.14.0-70.144.1.rt21.216.el9_02025-08-27redhat
redhatkernel-0:5.14.0-70.144.1.el9_02025-08-27redhat
redhatkernel-0:5.14.0-284.134.1.el9_22025-08-27redhat
redhatkernel-0:4.18.0-193.165.1.el8_22025-08-27redhat
redhatkernel-0:4.18.0-477.107.1.el8_82025-08-25redhat
redhatkernel-rt-0:4.18.0-553.64.1.rt7.405.el8_102025-07-28redhat
redhatkernel-0:4.18.0-553.64.1.el8_102025-07-28redhat
redhatkernel-0:5.14.0-427.13.1.el9_42024-04-30redhat

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-49977?
CVE-2022-49977 is a medium vulnerability published on June 18, 2025. In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix NULL pointer dereference in isftracetrampoline when ftrace is dead ftracestartup does not remove ops from ftraceops_list when ftracestartupenable fails: registerftracefunction ftrace_startup registerftracefunction ...…
When was CVE-2022-49977 disclosed?
CVE-2022-49977 was first published in the National Vulnerability Database on June 18, 2025, with the most recent update on November 14, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-49977 actively exploited?
CVE-2022-49977 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 11.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-49977?
CVE-2022-49977 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-49977?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-49977, 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-49977

Explore →

Is Your Infrastructure Affected by CVE-2022-49977?

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

Start Free Scan →Browse All CVEs