CVE-2026-53121

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-24. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

amd-pstate: Fix memory leak in amd_pstate_epp_cpu_init()

On failure to set the epp, the function amd_pstate_epp_cpu_init() returns with an error code without freeing the cpudata object that was allocated at the beginning of the function.

Ensure that the cpudata object is freed before returning from the function.

This memory leak was discovered by Claude Opus 4.6 with the aid of Chris Mason's AI review-prompts (https://github.com/masoncl/review-prompts/tree/main/kernel).

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

Published

June 24, 2026

Last Modified

July 23, 2026

Advisory Details (3)

Auto-updated Jul 24, 2026
No patch confirmed yet.
generic

amd-pstate: Fix memory leak in amd_pstate_epp_cpu_init() - kernel/git/stable/linux.git - Linux kernel stable tree

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

amd-pstate: Fix memory leak in amd_pstate_epp_cpu_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7f9aa2359742eaa6ea65ec0d20dafdfd0add9b8b
generic

amd-pstate: Fix memory leak in amd_pstate_epp_cpu_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/539aabbab190825c77eb455ec35652cb3720625f

Vendor Advisories for CVE-2026-53121(1)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1—

Weakness Classification(1)

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

All Vendor Advisories

(8)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 60× 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 170 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53121?
CVE-2026-53121 is a medium vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: amd-pstate: Fix memory leak in amdpstateeppcpuinit() On failure to set the epp, the function amdpstateeppcpuinit() returns with an error code without freeing the cpudata object that was allocated at the beginning of the function.…
When was CVE-2026-53121 disclosed?
CVE-2026-53121 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53121 actively exploited?
CVE-2026-53121 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 98.4% of all scored CVEs.
What is the CVSS score of CVE-2026-53121?
CVE-2026-53121 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53121?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53121, 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-2026-53121

Explore →

Is Your Infrastructure Affected by CVE-2026-53121?

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

Start Free Scan →Browse All CVEs