CVE-2022-50008

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-06-18. NVD baseline CVSS 5.5; sources differ by 0.0.

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

Also known asEUVD-2022-55287 (ENISA EUVD) · GHSA-q44m-58pc-8rr7 (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:

kprobes: don't call disarm_kprobe() for disabled kprobes

The assumption in __disable_kprobe() is wrong, and it could try to disarm an already disarmed kprobe and fire the WARN_ONCE() below. [0] We can easily reproduce this issue.

  • Write 0 to /sys/kernel/debug/kprobes/enabled.

# echo 0 > /sys/kernel/debug/kprobes/enabled

  • Run execsnoop. At this time, one kprobe is disabled.

# /usr/share/bcc/tools/execsnoop & [1] 2460 PCOMM PID PPID RET ARGS

# cat /sys/kernel/debug/kprobes/list ffffffff91345650 r __x64_sys_execve+0x0 [FTRACE] ffffffff91345650 k __x64_sys_execve+0x0 [DISABLED][FTRACE]

  • Write 1 to /sys/kernel/debug/kprobes/enabled, which changes
kprobes_all_disarmed to false but does not arm the disabled kprobe.

# echo 1 > /sys/kernel/debug/kprobes/enabled

# cat /sys/kernel/debug/kprobes/list ffffffff91345650 r __x64_sys_execve+0x0 [FTRACE] ffffffff91345650 k __x64_sys_execve+0x0 [DISABLED][FTRACE]

  • Kill execsnoop, when __disable_kprobe() calls disarm_kprobe() for the
disabled kprobe and hits the WARN_ONCE() in __disarm_kprobe_ftrace().

# fg /usr/share/bcc/tools/execsnoop ^C

Actually, WARN_ONCE() is fired twice, and __unregister_kprobe_top() misses some cleanups and leaves the aggregated kprobe in the hash table. Then, __unregister_trace_kprobe() initialises tk->rp.kp.list and creates an infinite loop like this.

aggregated kprobe.list -> kprobe.list -. ^ | '.__.'

In this situation, these commands fall into the infinite loop and result in RCU stall or soft lockup.

cat /sys/kernel/debug/kprobes/list : show_kprobe_addr() enters into the infinite loop with RCU.

/usr/share/bcc/tools/execsnoop : warn_kprobe_rereg() holds kprobe_mutex, and __get_valid_kprobe() is stuck in the loop.

To avoid the issue, make sure we don't call disarm_kprobe() for disabled kprobes.

[0] Failed to disarm kprobe-ftrace at __x64_sys_execve+0x0/0x40 (error -2) WARNING: CPU: 6 PID: 2460 at kernel/kprobes.c:1130 __disarm_kprobe_ftrace.isra.19 (kernel/kprobes.c:1129) Modules linked in: ena CPU: 6 PID: 2460 Comm: execsnoop Not tainted 5.19.0+ #28 Hardware name: Amazon EC2 c5.2xlarge/, BIOS 1.0 10/16/2017 RIP: 0010:__disarm_kprobe_ftrace.isra.19 (kernel/kprobes.c:1129) Code: 24 8b 02 eb c1 80 3d c4 83 f2 01 00 75 d4 48 8b 75 00 89 c2 48 c7 c7 90 fa 0f 92 89 04 24 c6 05 ab 83 01 e8 e4 94 f0 ff <0f> 0b 8b 04 24 eb b1 89 c6 48 c7 c7 60 fa 0f 92 89 04 24 e8 cc 94 RSP: 0018:ffff9e6ec154bd98 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffffffff930f7b00 RCX: 0000000000000001 RDX: 0000000080000001 RSI: ffffffff921461c5 RDI: 00000000ffffffff RBP: ffff89c504286da8 R08: 0000000000000000 R09: c0000000fffeffff R10: 0000000000000000 R11: ffff9e6ec154bc28 R12: ffff89c502394e40 R13: ffff89c502394c00 R14: ffff9e6ec154bc00 R15: 0000000000000000 FS: 00007fe800398740(0000) GS:ffff89c812d80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000c00057f010 CR3: 0000000103b54006 CR4: 00000000007706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace:

__disable_kprobe (kernel/kprobes.c:1716) disable_kprobe (kernel/kprobes.c:2392) __disable_trace_kprobe (kernel/trace/trace_kprobe.c:340) disable_trace_kprobe (kernel/trace/trace_kprobe.c:429) perf_trace_event_unreg.isra.2 (./include/linux/tracepoint.h:93 kernel/trace/trace_event_perf.c:168) perf_kprobe_destroy (kernel/trace/trace_event_perf.c:295) _free_event (kernel/events/core.c:4971) perf_event_release_kernel (kernel/events/core.c:5176) perf_release (kernel/events/core.c:5186) __fput (fs/file_table.c:321) task_work_run (./include/linux/ ---truncated---

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.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 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
16th
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

June 18, 2025

Last Modified

November 5, 2026

References (8)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 4.9.327 (fixes >=4.0.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 (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
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 33× 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 208 rows on record for this CVE, as 99 entries (1 repeat merged).

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 108 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-50008?
CVE-2022-50008 is a medium-severity vulnerability; its CVE record was published on June 18, 2025. In the Linux kernel, the following vulnerability has been resolved: kprobes: don't call disarm_kprobe() for disabled kprobes The assumption in __disable_kprobe() is wrong, and it could try to disarm an already disarmed kprobe and fire the WARN_ONCE() below. [0] We can easily reproduce this issue.…
When was the CVE record for CVE-2022-50008 published?
The CVE record for CVE-2022-50008 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-50008 actively exploited?
CVE-2022-50008 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-50008?
CVE-2022-50008 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-50008?
A fix for CVE-2022-50008 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-50008

Explore →

Is Your Infrastructure Affected by CVE-2022-50008?

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

Book a Demo →Browse All CVEs