CVE-2022-49341

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory (severity: MODERATE) published 2025-10-21. NVD baseline CVSS 5.5; 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-2022-54887 (ENISA EUVD) · GHSA-2c59-vh4j-7xh2 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

bpf, arm64: Clear prog->jited_len along prog->jited

syzbot reported an illegal copy_to_user() attempt from bpf_prog_get_info_by_fd() [1]

There was no repro yet on this bug, but I think that commit 0aef499f3172 ("mm/usercopy: Detect vmalloc overruns") is exposing a prior bug in bpf arm64.

bpf_prog_get_info_by_fd() looks at prog->jited_len to determine if the JIT image can be copied out to user space.

My theory is that syzbot managed to get a prog where prog->jited_len has been set to 43, while prog->bpf_func has ben cleared.

It is not clear why copy_to_user(uinsns, NULL, ulen) is triggering this particular warning.

I thought find_vma_area(NULL) would not find a vm_struct. As we do not hold vmap_area_lock spinlock, it might be possible that the found vm_struct was garbage.

[1] usercopy: Kernel memory exposure attempt detected from vmalloc (offset 792633534417210172, size 43)! kernel BUG at mm/usercopy.c:101! Internal error: Oops - BUG: 0 [#1] PREEMPT SMP Modules linked in: CPU: 0 PID: 25002 Comm: syz-executor.1 Not tainted 5.18.0-syzkaller-10139-g8291eaafed36 #0 Hardware name: linux,dummy-virt (DT) pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : usercopy_abort+0x90/0x94 mm/usercopy.c:101 lr : usercopy_abort+0x90/0x94 mm/usercopy.c:89 sp : ffff80000b773a20 x29: ffff80000b773a30 x28: faff80000b745000 x27: ffff80000b773b48 x26: 0000000000000000 x25: 000000000000002b x24: 0000000000000000 x23: 00000000000000e0 x22: ffff80000b75db67 x21: 0000000000000001 x20: 000000000000002b x19: ffff80000b75db3c x18: 00000000fffffffd x17: 2820636f6c6c616d x16: 76206d6f72662064 x15: 6574636574656420 x14: 74706d6574746120 x13: 2129333420657a69 x12: 73202c3237313031 x11: 3237313434333533 x10: 3336323937207465 x9 : 657275736f707865 x8 : ffff80000a30c550 x7 : ffff80000b773830 x6 : ffff80000b773830 x5 : 0000000000000000 x4 : ffff00007fbbaa10 x3 : 0000000000000000 x2 : 0000000000000000 x1 : f7ff000028fc0000 x0 : 0000000000000064 Call trace: usercopy_abort+0x90/0x94 mm/usercopy.c:89 check_heap_object mm/usercopy.c:186 [inline] __check_object_size mm/usercopy.c:252 [inline] __check_object_size+0x198/0x36c mm/usercopy.c:214 check_object_size include/linux/thread_info.h:199 [inline] check_copy_size include/linux/thread_info.h:235 [inline] copy_to_user include/linux/uaccess.h:159 [inline] bpf_prog_get_info_by_fd.isra.0+0xf14/0xfdc kernel/bpf/syscall.c:3993 bpf_obj_get_info_by_fd+0x12c/0x510 kernel/bpf/syscall.c:4253 __sys_bpf+0x900/0x2150 kernel/bpf/syscall.c:4956 __do_sys_bpf kernel/bpf/syscall.c:5021 [inline] __se_sys_bpf kernel/bpf/syscall.c:5019 [inline] __arm64_sys_bpf+0x28/0x40 kernel/bpf/syscall.c:5019 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x48/0x114 arch/arm64/kernel/syscall.c:52 el0_svc_common.constprop.0+0x44/0xec arch/arm64/kernel/syscall.c:142 do_el0_svc+0xa0/0xc0 arch/arm64/kernel/syscall.c:206 el0_svc+0x44/0xb0 arch/arm64/kernel/entry-common.c:624 el0t_64_sync_handler+0x1ac/0x1b0 arch/arm64/kernel/entry-common.c:642 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:581 Code: aa0003e3 d00038c0 91248000 97fff65f (d4210000)

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 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
20th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-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 (model v2026.06.15, score date 2026-11-05). 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

February 26, 2025

Last Modified

November 5, 2026

References (7)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 4.19.247 (fixes >=4.16.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 (14 versions)
  • every version up to 5.10.127-1: fixed in 5.10.127-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.5-1: fixed in 5.18.5-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.5-1: fixed in 5.18.5-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.5-1: fixed in 5.18.5-1
—

Data Freshness Timeline

(refreshed 10× in last 7d / 39× 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 98 of 198 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 100 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2022-49341?
CVE-2022-49341 is a medium-severity vulnerability; its CVE record was published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: bpf, arm64: Clear prog->jited_len along prog->jited syzbot reported an illegal copy_to_user() attempt from bpf_prog_get_info_by_fd() [1] There was no repro yet on this bug, but I think that commit 0aef499f3172 ("mm/usercopy: Detect…
When was the CVE record for CVE-2022-49341 published?
The CVE record for CVE-2022-49341 was published on February 26, 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-49341 actively exploited?
CVE-2022-49341 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49341?
CVE-2022-49341 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-49341?
A fix for CVE-2022-49341 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-49341

Explore →

Is Your Infrastructure Affected by CVE-2022-49341?

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

Book a Demo →Browse All CVEs