CVE-2022-50087

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-06-18. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails

When scpi probe fails, at any point, we need to ensure that the scpi_info is not set and will remain NULL until the probe succeeds. If it is not taken care, then it could result use-after-free as the value is exported via get_scpi_ops() and could refer to a memory allocated via devm_kzalloc() but freed when the probe fails.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

June 18, 2025

Last Modified

August 5, 2026

Advisory Details (7)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/689640efc0a2c4e07e6f88affe6d42cd40cc3f85
generic

firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4f2d7b46d6b53c07f44a4f8f8f4438888f0e9e87
generic

firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/87c4896d5dd7fd9927c814cf3c6289f41de3b562
generic

firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0c29e149b6bb498778ed8a1c9597b51acfba7856
generic

firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/08272646cd7c310642c39b7f54348fddd7987643
generic

firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/18048cba444a7c41dbf42c180d6b46606fc24c51
generic

firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5aa558232edc30468d1f35108826dd5b3ffe978f

Vendor Advisories for CVE-2022-50087(14)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(15)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-305.179.1.el8_42025-12-04redhat
redhatkernel-0:4.18.0-193.173.1.el8_22025-11-18redhat
redhatkernel-0:5.14.0-611.7.1.el9_72025-11-12redhat
redhatkernel-0:5.14.0-570.55.1.el9_62025-10-20redhat
redhatkernel-rt-0:5.14.0-70.149.1.rt21.221.el9_02025-10-15redhat
redhatkernel-0:4.18.0-372.164.1.el8_62025-10-15redhat
redhatkernel-0:5.14.0-70.149.1.el9_02025-10-15redhat
redhatkernel-0:5.14.0-427.94.1.el9_42025-10-14redhat
redhatkernel-rt-0:5.14.0-284.142.1.rt14.427.el9_22025-10-13redhat
redhatkernel-0:5.14.0-284.142.1.el9_22025-10-13redhat
redhatkernel-0:4.18.0-477.114.1.el8_82025-10-08redhat
redhatkernel-rt-0:4.18.0-553.77.1.rt7.418.el8_102025-09-29redhat
redhatkernel-0:4.18.0-553.77.1.el8_102025-09-29redhat
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 4.19.256—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 rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (18 versions)5.10.140-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.2-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.2-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.2-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 149 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2022-50087?
CVE-2022-50087 is a high vulnerability published on June 18, 2025. In the Linux kernel, the following vulnerability has been resolved: firmware: armscpi: Ensure scpiinfo is not assigned if the probe fails When scpi probe fails, at any point, we need to ensure that the scpi_info is not set and will remain NULL until the probe succeeds. If it is not taken care, then…
When was CVE-2022-50087 disclosed?
CVE-2022-50087 was first published in the National Vulnerability Database on June 18, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-50087 actively exploited?
CVE-2022-50087 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.3% of all scored CVEs.
What is the CVSS score of CVE-2022-50087?
CVE-2022-50087 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-50087?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50087, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2022-50087?

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

Start Free Scan →Browse All CVEs