Improper handling of overlap between protected memory ranges for some Intel(R) Xeon(R) 6 processors when using Intel(R) TDX within SMM may allow an escalation of privilege. SMM 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 requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.
CVE-2025-31936
Score 5.7 from GitHub Security Advisory (severity: HIGH) published 2026-08-11. NVD baseline CVSS 5.7; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.7
- EG Score
- 5.7MEDIUMmedium confidence
- EG Risk
- 26EG Risk 26/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 computedSeverity57% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).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 low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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 11, 2026INTEL-SA-01379
https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01379.htmlVendor Advisories for CVE-2025-31936(4)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:68011Red Hat Product SecurityHigh
Red Hat Security Advisory: microcode_ctl security, bug fix, and enhancement update
- RHSA-2026:67979Red Hat Product SecurityHigh
Red Hat Security Advisory: microcode_ctl security, bug fix, and enhancement update
- RHSA-2026:65147Red Hat Product SecurityHigh
Red Hat Security Advisory: microcode_ctl security, bug fix, and enhancement update
- GHSA-v7w9-9v5r-766hGitHub Security AdvisoriesHigh
Improper handling of overlap between protected memory ranges for some Intel(R) Xeon(R) 6...
Patch Availability(3)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | microcode_ctl-4:20260210-1.20260812.1.el9_8 | 2026-09-16 | redhat |
| redhat | microcode_ctl-4:20260812-0.el10_2 | 2026-09-16 | redhat |
| redhat | microcode_ctl-4:20260812-1.el8_10 | 2026-09-08 | redhat |
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
(3 across 3 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| intel-microcode | 0.20080131-1 ... 3.20260227.1 (210 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| intel-microcode | 0.20080131-1 ... 3.20260227.1 (210 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| intel-microcode | 0.20080131-1 ... 3.20260227.1 (210 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 18× in last 7d / 112× 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 205 total refreshes for this CVE.
- 2026-10-04 22:44 UTCVendor advisory
- 2026-10-04 22:44 UTCGHSA enrichment
- 2026-10-03 20:57 UTCEG score recompute
- 2026-10-03 20:57 UTCVendor advisory
- 2026-10-03 20:57 UTCGHSA enrichment
- 2026-10-03 14:24 UTCEPSS rescore
- 2026-10-02 08:41 UTCEG score recompute
- 2026-10-02 08:41 UTCVendor advisory
- 2026-10-02 08:41 UTCGHSA enrichment
- 2026-10-01 19:49 UTCEPSS rescore
- 2026-09-30 22:16 UTCEG score recompute
- 2026-09-30 22:16 UTCVendor advisory
- 2026-09-30 22:16 UTCGHSA enrichment
- 2026-09-30 15:02 UTCEPSS rescore
- 2026-09-29 15:19 UTCEPSS rescore
- 2026-09-29 11:14 UTCEG score recompute
- 2026-09-29 11:14 UTCVendor advisory
- 2026-09-29 11:13 UTCGHSA enrichment
- 2026-09-28 10:24 UTCEG score recompute
- 2026-09-28 10:24 UTCVendor advisory
- 2026-09-28 10:24 UTCGHSA enrichment
- 2026-09-27 10:13 UTCEG score recompute
- 2026-09-27 10:13 UTCVendor advisory
- 2026-09-27 10:13 UTCGHSA enrichment
- 2026-09-26 15:58 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-09-26 15:58 UTCEPSS rescore
- 2026-09-26 00:24 UTCEPSS rescore
- 2026-09-26 00:24 UTCEPSS rescore
- 2026-09-25 03:54 UTCEG score recompute
- 2026-09-25 03:54 UTCVendor advisory
- 2026-09-25 03:54 UTCGHSA enrichment
- 2026-09-24 14:02 UTCEPSS rescore
- 2026-09-23 21:30 UTCVendor advisory
- 2026-09-23 21:30 UTCGHSA enrichment
- 2026-09-22 21:19 UTCEG score recompute
- 2026-09-22 21:19 UTCVendor advisory
- 2026-09-22 21:19 UTCGHSA enrichment
- 2026-09-21 21:08 UTCEG score recompute
- 2026-09-21 21:08 UTCVendor advisory
- 2026-09-21 21:08 UTCGHSA enrichment
- 2026-09-20 19:27 UTCEG score recompute
- 2026-09-20 19:27 UTCVendor advisory
- 2026-09-20 19:27 UTCGHSA enrichment
- 2026-09-19 14:43 UTCEG score recompute
- 2026-09-19 14:43 UTCVendor advisory
- 2026-09-19 14:43 UTCGHSA enrichment
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-18 14:22 UTCEG score recompute▼ 1.30
- 2026-09-18 14:22 UTCVendor advisory
- 2026-09-18 14:22 UTCGHSA enrichment
- 2026-09-18 14:20 UTCNVD updateCVSS v3 → 5.7 · severity → MEDIUM
- 2026-09-18 02:09 UTCEG score recompute
- 2026-09-18 02:09 UTCVendor advisory
- 2026-09-18 02:09 UTCGHSA enrichment
- 2026-09-17 13:53 UTCVendor advisory
- 2026-09-17 13:53 UTCGHSA enrichment
- 2026-09-17 00:31 UTCEG score recompute
- 2026-09-17 00:31 UTCVendor advisory
- 2026-09-17 00:31 UTCGHSA enrichment
- 2026-09-16 14:07 UTCEPSS rescore
- 2026-09-16 05:13 UTCEPSS rescore
- 2026-09-16 01:59 UTCVendor advisory
- 2026-09-16 01:59 UTCGHSA enrichment
- 2026-09-15 13:22 UTCEG score recompute
- 2026-09-15 13:22 UTCVendor advisory
- 2026-09-15 13:22 UTCGHSA enrichment
- 2026-09-14 22:41 UTCVendor advisory
- 2026-09-14 22:41 UTCGHSA enrichment
- 2026-09-14 08:32 UTCVendor advisory
- 2026-09-14 08:32 UTCGHSA enrichment
- 2026-09-13 20:17 UTCEG score recompute
- 2026-09-13 20:17 UTCVendor advisory
- 2026-09-13 20:17 UTCGHSA enrichment
- 2026-09-13 16:46 UTCEPSS rescore
- 2026-09-13 08:01 UTCVendor advisory
- 2026-09-13 08:01 UTCGHSA enrichment
- 2026-09-12 19:46 UTCEG score recompute
- 2026-09-12 19:46 UTCVendor advisory
- 2026-09-12 19:46 UTCGHSA enrichment
- 2026-09-12 15:00 UTCEPSS rescore
- 2026-09-12 07:31 UTCVendor advisory
- 2026-09-12 07:30 UTCGHSA enrichment
- 2026-09-11 19:14 UTCEG score recompute
- 2026-09-11 19:14 UTCVendor advisory
- 2026-09-11 19:14 UTCGHSA enrichment
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-11 09:35 UTCEPSS rescore
- 2026-09-11 06:53 UTCVendor advisory
- 2026-09-11 06:53 UTCGHSA enrichment
- 2026-09-10 18:38 UTCEG score recompute
- 2026-09-10 18:38 UTCVendor advisory
- 2026-09-10 18:37 UTCGHSA enrichment
- 2026-09-10 09:33 UTCEPSS rescore
- 2026-09-10 06:19 UTCVendor advisory
- 2026-09-10 06:19 UTCGHSA enrichment
- 2026-09-09 18:00 UTCVendor advisory
- 2026-09-09 18:00 UTCGHSA enrichment
- 2026-09-09 05:38 UTCEG score recompute
- 2026-09-09 05:38 UTCVendor advisory
- 2026-09-09 05:38 UTCGHSA enrichment
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownDebian:12:intel-microcode
Frequently asked(5)
What is CVE-2025-31936?
When was CVE-2025-31936 disclosed?
Is CVE-2025-31936 actively exploited?
What is the CVSS score of CVE-2025-31936?
How do I remediate CVE-2025-31936?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-31936
Is Your Infrastructure Affected by CVE-2025-31936?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.