CVE-2022-50553

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 published 2025-10-07. 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-2025-31984 (ENISA EUVD) · GHSA-rvj3-h2c8-jjxg (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.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

tracing/hist: Fix out-of-bound write on 'action_data.var_ref_idx'

When generate a synthetic event with many params and then create a trace action for it [1], kernel panic happened [2].

It is because that in trace_action_create() 'data->n_params' is up to SYNTH_FIELDS_MAX (current value is 64), and array 'data->var_ref_idx' keeps indices into array 'hist_data->var_refs' for each synthetic event param, but the length of 'data->var_ref_idx' is TRACING_MAP_VARS_MAX (current value is 16), so out-of-bound write happened when 'data->n_params' more than 16. In this case, 'data->match_data.event' is overwritten and eventually cause the panic.

To solve the issue, adjust the length of 'data->var_ref_idx' to be SYNTH_FIELDS_MAX and add sanity checks to avoid out-of-bound write.

[1] # cd /sys/kernel/tracing/ # echo "my_synth_event int v1; int v2; int v3; int v4; int v5; int v6;\ int v7; int v8; int v9; int v10; int v11; int v12; int v13; int v14;\ int v15; int v16; int v17; int v18; int v19; int v20; int v21; int v22;\ int v23; int v24; int v25; int v26; int v27; int v28; int v29; int v30;\ int v31; int v32; int v33; int v34; int v35; int v36; int v37; int v38;\ int v39; int v40; int v41; int v42; int v43; int v44; int v45; int v46;\ int v47; int v48; int v49; int v50; int v51; int v52; int v53; int v54;\ int v55; int v56; int v57; int v58; int v59; int v60; int v61; int v62;\ int v63" >> synthetic_events # echo 'hist:keys=pid:ts0=common_timestamp.usecs if comm=="bash"' >> \ events/sched/sched_waking/trigger # echo "hist:keys=next_pid:onmatch(sched.sched_waking).my_synth_event(\ pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,\ pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,\ pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,\ pid,pid,pid,pid,pid,pid,pid,pid,pid)" >> events/sched/sched_switch/trigger

[2] BUG: unable to handle page fault for address: ffff91c900000000 PGD 61001067 P4D 61001067 PUD 0 Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 2 PID: 322 Comm: bash Tainted: G W 6.1.0-rc8+ #229 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014 RIP: 0010:strcmp+0xc/0x30 Code: 75 f7 31 d2 44 0f b6 04 16 44 88 04 11 48 83 c2 01 45 84 c0 75 ee c3 cc cc cc cc 0f 1f 00 31 c0 eb 08 48 83 c0 01 84 d2 74 13 <0f> b6 14 07 3a 14 06 74 ef 19 c0 83 c8 01 c3 cc cc cc cc 31 c3 RSP: 0018:ffff9b3b00f53c48 EFLAGS: 00000246 RAX: 0000000000000000 RBX: ffffffffba958a68 RCX: 0000000000000000 RDX: 0000000000000010 RSI: ffff91c943d33a90 RDI: ffff91c900000000 RBP: ffff91c900000000 R08: 00000018d604b529 R09: 0000000000000000 R10: ffff91c9483eddb1 R11: ffff91ca483eddab R12: ffff91c946171580 R13: ffff91c9479f0538 R14: ffff91c9457c2848 R15: ffff91c9479f0538 FS: 00007f1d1cfbe740(0000) GS:ffff91c9bdc80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffff91c900000000 CR3: 0000000006316000 CR4: 00000000000006e0 Call Trace: __find_event_file+0x55/0x90 action_create+0x76c/0x1060 event_hist_trigger_parse+0x146d/0x2060 ? event_trigger_write+0x31/0xd0 trigger_process_regex+0xbb/0x110 event_trigger_write+0x6b/0xd0 vfs_write+0xc8/0x3e0 ? alloc_fd+0xc0/0x160 ? preempt_count_add+0x4d/0xa0 ? preempt_count_add+0x70/0xa0 ksys_write+0x5f/0xe0 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f1d1d0cf077 Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 RSP: 002b:00007ffcebb0e568 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 0000000000000143 RCX: 00007f1d1d0cf077 RDX: 0000000000000143 RSI: 00005639265aa7e0 RDI: 0000000000000001 RBP: 00005639265aa7e0 R08: 000000000000000a R09: 0000000000000142 R ---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 BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
10th
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.2% within 30 daysSource: FIRST EPSS. 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 (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

October 7, 2025

Last Modified

February 4, 2026

References (6)

Patch Availability(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 34× 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 95 of 182 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 87 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% · 10th percentile
  2. 2026-11-01 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-10-31 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  5. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-28 16:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-27 16:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-25 17:53 UTCEG score recompute
  10. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-10-24 17:40 UTCEG score recompute
  12. 2026-10-24 17:40 UTCGHSA enrichmentGHSA-rvj3-h2c8-jjxg · GitHub CVSS 5.5
  13. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-10-22 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  17. 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-10-18 08:18 UTCEG score recompute
  20. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-10-15 16:28 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-10-12 18:40 UTCEG score recompute
Show 70 more
  1. 2026-10-11 22:04 UTCEG score recompute
  2. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  3. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  4. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  5. 2026-10-08 17:05 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  7. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  8. 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  9. 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  10. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  11. 2026-10-02 03:40 UTCOSV refresh
  12. 2026-09-30 16:13 UTCEG score recompute
  13. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-09-26 15:55 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  17. 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-09-20 20:13 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  22. 2026-09-15 03:07 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  23. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  24. 2026-09-12 21:36 UTCOSV refresh
  25. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  26. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  27. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  28. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  29. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  30. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  31. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  32. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  33. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  34. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  35. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  36. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  37. 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  38. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  39. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  40. 2026-08-25 02:26 UTCOSV refresh
  41. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  42. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  43. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  44. 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  45. 2026-08-18 13:45 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  46. 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  47. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  48. 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  49. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  50. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  51. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  52. 2026-08-08 19:49 UTCOSV refresh
  53. 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  54. 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  55. 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  56. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  57. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  58. 2026-08-03 10:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  59. 2026-08-02 02:24 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  60. 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  61. 2026-07-30 16:25 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  62. 2026-07-30 01:28 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  63. 2026-07-28 15:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  64. 2026-07-26 14:52 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  65. 2026-07-24 14:15 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  66. 2026-07-23 18:41 UTCOSV refresh
  67. 2026-07-23 14:16 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  68. 2026-07-23 02:17 UTCEG score recompute
  69. 2026-07-22 23:04 UTCEG score recompute
  70. 2026-07-22 14:06 UTCEPSS rescoreEPSS 0.2% · 9th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-50553?
CVE-2022-50553 is a medium-severity vulnerability; its CVE record was published on October 7, 2025. In the Linux kernel, the following vulnerability has been resolved: tracing/hist: Fix out-of-bound write on 'action_data.var_ref_idx' When generate a synthetic event with many params and then create a trace action for it [1], kernel panic happened [2]. It is because that in trace_action_create()…
When was the CVE record for CVE-2022-50553 published?
The CVE record for CVE-2022-50553 was published on October 7, 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 February 4, 2026; the record at its source may have been updated since.
Is CVE-2022-50553 actively exploited?
CVE-2022-50553 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-50553?
CVE-2022-50553 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-50553?
A fix for CVE-2022-50553 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-50553

Explore →

Is Your Infrastructure Affected by CVE-2022-50553?

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

Book a Demo →Browse All CVEs