CVE-2022-50054

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-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
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:

iavf: Fix NULL pointer dereference in iavf_get_link_ksettings

Fix possible NULL pointer dereference, due to freeing of adapter->vf_res in iavf_init_get_resources. Previous commit introduced a regression, where receiving IAVF_ERR_ADMIN_QUEUE_NO_WORK from iavf_get_vf_config would free adapter->vf_res. However, netdev is still registered, so ethtool_ops can be called. Calling iavf_get_link_ksettings with no vf_res, will result with: [ 9385.242676] BUG: kernel NULL pointer dereference, address: 0000000000000008 [ 9385.242683] #PF: supervisor read access in kernel mode [ 9385.242686] #PF: error_code(0x0000) - not-present page [ 9385.242690] PGD 0 P4D 0 [ 9385.242696] Oops: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC PTI [ 9385.242701] CPU: 6 PID: 3217 Comm: pmdalinux Kdump: loaded Tainted: G S E 5.18.0-04958-ga54ce3703613-dirty #1 [ 9385.242708] Hardware name: Dell Inc. PowerEdge R730/0WCJNT, BIOS 2.11.0 11/02/2019 [ 9385.242710] RIP: 0010:iavf_get_link_ksettings+0x29/0xd0 [iavf] [ 9385.242745] Code: 00 0f 1f 44 00 00 b8 01 ef ff ff 48 c7 46 30 00 00 00 00 48 c7 46 38 00 00 00 00 c6 46 0b 00 66 89 46 08 48 8b 87 68 0e 00 00 40 08 80 75 50 8b 87 5c 0e 00 00 83 f8 08 74 7a 76 1d 83 f8 20 [ 9385.242749] RSP: 0018:ffffc0560ec7fbd0 EFLAGS: 00010246 [ 9385.242755] RAX: 0000000000000000 RBX: ffffc0560ec7fc08 RCX: 0000000000000000 [ 9385.242759] RDX: ffffffffc0ad4550 RSI: ffffc0560ec7fc08 RDI: ffffa0fc66674000 [ 9385.242762] RBP: 00007ffd1fb2bf50 R08: b6a2d54b892363ee R09: ffffa101dc14fb00 [ 9385.242765] R10: 0000000000000000 R11: 0000000000000004 R12: ffffa0fc66674000 [ 9385.242768] R13: 0000000000000000 R14: ffffa0fc66674000 R15: 00000000ffffffa1 [ 9385.242771] FS: 00007f93711a2980(0000) GS:ffffa0fad72c0000(0000) knlGS:0000000000000000 [ 9385.242775] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 9385.242778] CR2: 0000000000000008 CR3: 0000000a8e61c003 CR4: 00000000003706e0 [ 9385.242781] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 9385.242784] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 9385.242787] Call Trace: [ 9385.242791] [ 9385.242793] ethtool_get_settings+0x71/0x1a0 [ 9385.242814] __dev_ethtool+0x426/0x2f40 [ 9385.242823] ? slab_post_alloc_hook+0x4f/0x280 [ 9385.242836] ? kmem_cache_alloc_trace+0x15d/0x2f0 [ 9385.242841] ? dev_ethtool+0x59/0x170 [ 9385.242848] dev_ethtool+0xa7/0x170 [ 9385.242856] dev_ioctl+0xc3/0x520 [ 9385.242866] sock_do_ioctl+0xa0/0xe0 [ 9385.242877] sock_ioctl+0x22f/0x320 [ 9385.242885] __x64_sys_ioctl+0x84/0xc0 [ 9385.242896] do_syscall_64+0x3a/0x80 [ 9385.242904] entry_SYSCALL_64_after_hwframe+0x46/0xb0 [ 9385.242918] RIP: 0033:0x7f93702396db [ 9385.242923] Code: 73 01 c3 48 8b 0d ad 57 38 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 7d 57 38 00 f7 d8 64 89 01 48 [ 9385.242927] RSP: 002b:00007ffd1fb2bf18 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 9385.242932] RAX: ffffffffffffffda RBX: 000055671b1d2fe0 RCX: 00007f93702396db [ 9385.242935] RDX: 00007ffd1fb2bf20 RSI: 0000000000008946 RDI: 0000000000000007 [ 9385.242937] RBP: 00007ffd1fb2bf20 R08: 0000000000000003 R09: 0030763066307330 [ 9385.242940] R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffd1fb2bf80 [ 9385.242942] R13: 0000000000000007 R14: 0000556719f6de90 R15: 00007ffd1fb2c1b0 [ 9385.242948] [ 9385.242949] Modules linked in: iavf(E) xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nft_compat nf_nat_tftp nft_objref nf_conntrack_tftp bridge stp llc nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables rfkill nfnetlink vfat fat irdma ib_uverbs ib_core intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretem ---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
5th
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: 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.

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

June 18, 2025

Last Modified

November 13, 2025

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-284.11.1.el9_22023-05-09redhat
redhatkernel-0:5.14.0-162.12.1.el9_12023-01-23redhat
redhatkernel-0:4.18.0-425.3.1.el82022-11-08redhat
redhatkernel-0:4.18.0-372.32.1.el8_62022-10-25redhat
linuxKernel @ 5.19.4 (fixes >=5.17.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

(3 across 3 ecosystems)
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 8× in last 7d / 29× 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 91 of 171 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. 9 repeat rows among the latest 100 are merged into the row they repeat. The 80 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2022-50054?
CVE-2022-50054 is a medium-severity vulnerability; its CVE record was published on June 18, 2025. In the Linux kernel, the following vulnerability has been resolved: iavf: Fix NULL pointer dereference in iavfgetlink_ksettings Fix possible NULL pointer dereference, due to freeing of adapter->vf_res in iavfinitget_resources. Previous commit introduced a regression, where receiving…
When was the CVE record for CVE-2022-50054 published?
The CVE record for CVE-2022-50054 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 13, 2025; the record at its source may have been updated since.
Is CVE-2022-50054 actively exploited?
CVE-2022-50054 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-50054?
CVE-2022-50054 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-50054?
A fix for CVE-2022-50054 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-50054 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2022-50054?

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