CVE-2022-49892

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

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, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2025-12863 (ENISA EUVD) · GHSA-w983-x7cf-qq48 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
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.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ftrace: Fix use-after-free for dynamic ftrace_ops

KASAN reported a use-after-free with ftrace ops [1]. It was found from vmcore that perf had registered two ops with the same content successively, both dynamic. After unregistering the second ops, a use-after-free occurred.

In ftrace_shutdown(), when the second ops is unregistered, the FTRACE_UPDATE_CALLS command is not set because there is another enabled ops with the same content. Also, both ops are dynamic and the ftrace callback function is ftrace_ops_list_func, so the FTRACE_UPDATE_TRACE_FUNC command will not be set. Eventually the value of 'command' will be 0 and ftrace_shutdown() will skip the rcu synchronization.

However, ftrace may be activated. When the ops is released, another CPU may be accessing the ops. Add the missing synchronization to fix this problem.

[1] BUG: KASAN: use-after-free in __ftrace_ops_list_func kernel/trace/ftrace.c:7020 [inline] BUG: KASAN: use-after-free in ftrace_ops_list_func+0x2b0/0x31c kernel/trace/ftrace.c:7049 Read of size 8 at addr ffff56551965bbc8 by task syz-executor.2/14468

CPU: 1 PID: 14468 Comm: syz-executor.2 Not tainted 5.10.0 #7 Hardware name: linux,dummy-virt (DT) Call trace: dump_backtrace+0x0/0x40c arch/arm64/kernel/stacktrace.c:132 show_stack+0x30/0x40 arch/arm64/kernel/stacktrace.c:196 __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1b4/0x248 lib/dump_stack.c:118 print_address_description.constprop.0+0x28/0x48c mm/kasan/report.c:387 __kasan_report mm/kasan/report.c:547 [inline] kasan_report+0x118/0x210 mm/kasan/report.c:564 check_memory_region_inline mm/kasan/generic.c:187 [inline] __asan_load8+0x98/0xc0 mm/kasan/generic.c:253 __ftrace_ops_list_func kernel/trace/ftrace.c:7020 [inline] ftrace_ops_list_func+0x2b0/0x31c kernel/trace/ftrace.c:7049 ftrace_graph_call+0x0/0x4 __might_sleep+0x8/0x100 include/linux/perf_event.h:1170 __might_fault mm/memory.c:5183 [inline] __might_fault+0x58/0x70 mm/memory.c:5171 do_strncpy_from_user lib/strncpy_from_user.c:41 [inline] strncpy_from_user+0x1f4/0x4b0 lib/strncpy_from_user.c:139 getname_flags+0xb0/0x31c fs/namei.c:149 getname+0x2c/0x40 fs/namei.c:209 [...]

Allocated by task 14445: kasan_save_stack+0x24/0x50 mm/kasan/common.c:48 kasan_set_track mm/kasan/common.c:56 [inline] __kasan_kmalloc mm/kasan/common.c:479 [inline] __kasan_kmalloc.constprop.0+0x110/0x13c mm/kasan/common.c:449 kasan_kmalloc+0xc/0x14 mm/kasan/common.c:493 kmem_cache_alloc_trace+0x440/0x924 mm/slub.c:2950 kmalloc include/linux/slab.h:563 [inline] kzalloc include/linux/slab.h:675 [inline] perf_event_alloc.part.0+0xb4/0x1350 kernel/events/core.c:11230 perf_event_alloc kernel/events/core.c:11733 [inline] __do_sys_perf_event_open kernel/events/core.c:11831 [inline] __se_sys_perf_event_open+0x550/0x15f4 kernel/events/core.c:11723 __arm64_sys_perf_event_open+0x6c/0x80 kernel/events/core.c:11723 [...]

Freed by task 14445: kasan_save_stack+0x24/0x50 mm/kasan/common.c:48 kasan_set_track+0x24/0x34 mm/kasan/common.c:56 kasan_set_free_info+0x20/0x40 mm/kasan/generic.c:358 __kasan_slab_free.part.0+0x11c/0x1b0 mm/kasan/common.c:437 __kasan_slab_free mm/kasan/common.c:445 [inline] kasan_slab_free+0x2c/0x40 mm/kasan/common.c:446 slab_free_hook mm/slub.c:1569 [inline] slab_free_freelist_hook mm/slub.c:1608 [inline] slab_free mm/slub.c:3179 [inline] kfree+0x12c/0xc10 mm/slub.c:4176 perf_event_alloc.part.0+0xa0c/0x1350 kernel/events/core.c:11434 perf_event_alloc kernel/events/core.c:11733 [inline] __do_sys_perf_event_open kernel/events/core.c:11831 [inline] __se_sys_perf_event_open+0x550/0x15f4 kernel/events/core.c:11723 [...]

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.2%
EPSS %ILE
12th
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.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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

May 1, 2025

Last Modified

October 15, 2026

Advisory Details (4)

Auto-updated Aug 4, 2026
Patch available.
Web page

ftrace: Fix use-after-free for dynamic ftrace_ops - kernel/git/stable/linux.git - Linux kernel stable tree

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

ftrace: Fix use-after-free for dynamic ftrace_ops - kernel/git/stable/linux.git - Linux kernel stable tree

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

ftrace: Fix use-after-free for dynamic ftrace_ops - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/88561a66777e7a2fe06638c6dcb22a9fae0b6733
Web page

ftrace: Fix use-after-free for dynamic ftrace_ops - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0e792b89e6800cd9cb4757a76a96f7ef3e8b6294

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 5.10.154 (fixes >=4.14.0)—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 (22 versions)
  • every version up to 5.10.158-1: fixed in 5.10.158-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.8-1: fixed in 6.0.8-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.8-1: fixed in 6.0.8-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.8-1: fixed in 6.0.8-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 40× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 99 of 203 refreshes 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 104 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-49892?
CVE-2022-49892 is a high-severity vulnerability; its CVE record was published on May 1, 2025. In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix use-after-free for dynamic ftrace_ops KASAN reported a use-after-free with ftrace ops [1]. It was found from vmcore that perf had registered two ops with the same content successively, both dynamic. After unregistering…
When was the CVE record for CVE-2022-49892 published?
The CVE record for CVE-2022-49892 was published on May 1, 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 October 15, 2026; the record at its source may have been updated since.
Is CVE-2022-49892 actively exploited?
CVE-2022-49892 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49892?
CVE-2022-49892 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-49892?
A fix for CVE-2022-49892 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2022-49892?

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

Book a Demo →Browse All CVEs