CVE-2022-50677

HIGHPre-NVD 7.07.0
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2025-12-09. the CNA's CVSS baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.0EG
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.0Exploit: None knownExposed: 0

A fix is available — apply it.

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

ipmi: fix use after free in _ipmi_destroy_user()

The intf_free() function frees the "intf" pointer so we cannot dereference it again on the next line.

CVSS v3
7.0
EG Score
7.0(medium)
EG Risk
36(Track)
EG Risk 36/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
Severity70% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

December 9, 2025

Last Modified

August 5, 2026

Advisory Details (7)

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

ipmi: fix use after free in _ipmi_destroy_user() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a92ce570c81dc0feaeb12a429b4bc65686d17967
generic

ipmi: fix use after free in _ipmi_destroy_user() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1fc9b20a7688000fcf4d7fbaa58e415a3cdda961
generic

ipmi: fix use after free in _ipmi_destroy_user() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f7fde441198a9ecb130c3ccec91ee2131d6998ee
generic

ipmi: fix use after free in _ipmi_destroy_user() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bfce073089cb81482521c65061835aaa6d1a6cc0
generic

ipmi: fix use after free in _ipmi_destroy_user() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f29d127b372e1b7662397d92341d9f7de198ff99
generic

ipmi: fix use after free in _ipmi_destroy_user() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d23006f2a56e11a3103de0ca8b843bf7fd7d76fc
generic

ipmi: fix use after free in _ipmi_destroy_user() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/35ad87bfe330f7ef6a19f772223c63296d643172

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-513.5.1.el8_92023-11-14redhat
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
redhatkernel-0:4.18.0-477.21.1.el8_82023-08-08redhat
linuxKernel @ 4.19.270osv

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 (25 versions)5.10.178-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.4-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.1.4-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.1.4-1

Data Freshness Timeline

(refreshed 4× 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 201 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2022-50677?
CVE-2022-50677 is a high vulnerability published on December 9, 2025. In the Linux kernel, the following vulnerability has been resolved: ipmi: fix use after free in ipmidestroy_user() The intf_free() function frees the "intf" pointer so we cannot dereference it again on the next line.
When was CVE-2022-50677 disclosed?
CVE-2022-50677 was first published in the National Vulnerability Database on December 9, 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-50677 actively exploited?
CVE-2022-50677 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.0% of all scored CVEs.
What is the CVSS score of CVE-2022-50677?
CVE-2022-50677 has a CVSS v4.0 base score of 7.0 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2022-50677?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50677, 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-50677

Explore →

Is Your Infrastructure Affected by CVE-2022-50677?

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