CVE-2025-68195

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2025-12-16. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.1EG
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.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

x86/CPU/AMD: Add missing terminator for zen5_rdseed_microcode

Running x86_match_min_microcode_rev() on a Zen5 CPU trips up KASAN for an out of bounds access.

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

Published

December 16, 2025

Last Modified

July 30, 2026

References (2)

Vendor Advisories for CVE-2025-68195(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 45× 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 132 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-68195?
CVE-2025-68195 is a high vulnerability published on December 16, 2025. In the Linux kernel, the following vulnerability has been resolved: x86/CPU/AMD: Add missing terminator for zen5rdseedmicrocode Running x86matchminmicrocoderev() on a Zen5 CPU trips up KASAN for an out of bounds access.
When was CVE-2025-68195 disclosed?
CVE-2025-68195 was first published in the National Vulnerability Database on December 16, 2025, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-68195 actively exploited?
CVE-2025-68195 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 97.7% of all scored CVEs.
What is the CVSS score of CVE-2025-68195?
CVE-2025-68195 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2025-68195?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-68195, 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

Explore the affected products and dependency analysis for CVE-2025-68195

Explore →

Is Your Infrastructure Affected by CVE-2025-68195?

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

Start Free Scan →Browse All CVEs