CVE-2025-35973

MEDIUMPre-NVD 4.54.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (below the 1st percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
4.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 4.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper handling of values for some Intel(R) Processors within Ring 0: Kernel, Hypervisor and Bare Metal OS may allow an escalation of privilege. Authorized adversary with a privileged user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are present with special internal knowledge and require no user interaction. The potential vulnerability may impact the confidentiality (low), integrity (low) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (high), integrity (high) and availability (none) impacts.

CVSS v3
4.5
EG Score
4.5MEDIUMmedium confidence
EG Risk
20
EG Risk 20/100CISA SSVC

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
Severity45% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
below the 1st
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 11, 2026

Last Modified

September 29, 2026

Advisory Details (1)

Auto-updated Aug 12, 2026
Patch available.
generic

INTEL-SA-01428

https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01428.html

Vendor Advisories for CVE-2025-35973(5)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatmicrocode_ctl-4:20260812-0.el10_22026-09-16redhat
redhatmicrocode_ctl-4:20260210-1.20260812.1.el9_82026-09-16redhat
redhatmicrocode_ctl-4:20260812-1.el8_102026-09-08redhat

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

(7 across 7 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
intel-ucode—
  • every version up to 20260812-r0: fixed in 20260812-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
intel-ucode—
  • every version up to 20260812-r0: fixed in 20260812-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
intel-ucode—
  • every version up to 20260812-r0: fixed in 20260812-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
intel-ucode—
  • every version up to 20260812-r0: fixed in 20260812-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
intel-microcode0.20080131-1 ... 3.20260227.1 (210 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
intel-microcode0.20080131-1 ... 3.20260227.1 (210 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
intel-microcode0.20080131-1 ... 3.20260227.1 (210 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 87× 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 153 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Same vendor

1 shown

redhat:RHSA-2026:65147

Frequently asked(5)

What is CVE-2025-35973?
CVE-2025-35973 is a medium vulnerability published on August 11, 2026. Improper handling of values for some Intel(R) Processors within Ring 0: Kernel, Hypervisor and Bare Metal OS may allow an escalation of privilege. Authorized adversary with a privileged user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur…
When was CVE-2025-35973 disclosed?
CVE-2025-35973 was first published on August 11, 2026, with the most recent update on September 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-35973 actively exploited?
CVE-2025-35973 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-35973?
CVE-2025-35973 has a CVSS base score of 4.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-35973?
A fix for CVE-2025-35973 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-35973 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-2025-35973

Explore →

Is Your Infrastructure Affected by CVE-2025-35973?

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

Book a Demo →Browse All CVEs