Incorrect behavior order for some Intel(R) Core™ Ultra Processors may allow an unauthenticated user to potentially enable information disclosure via physical access.
CVE-2025-20012
Score 4.9 from GitHub Security Advisory published 2025-05-13. NVD baseline CVSS 4.9; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 4.9
- EG Score
- 4.9(medium)
- EG Risk
- —
- EPSS
- 10.4%
- KEV
- Not listed
Published
May 13, 2025
Last Modified
April 15, 2026
References (2)
- secure@intelhttps://intel.com/content/www/us/en/security-center/advisory/intel-sa-01322.html
- af854a3a-2127-422b-91ae-364da2661108https://lists.debian.org/debian-lts-announce/2025/05/msg00021.html
Vendor Advisories for CVE-2025-20012(11)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2025:10991Red Hat Product SecurityMedium
Red Hat Security Advisory: microcode_ctl security update
- RHSA-2025:10162Red Hat Product SecurityMedium
Red Hat Security Advisory: microcode_ctl security update
- RHSA-2025:10109Red Hat Product SecurityMedium
Red Hat Security Advisory: microcode_ctl security update
- RHSA-2025:10126Red Hat Product SecurityMedium
Red Hat Security Advisory: microcode_ctl security update
- RHSA-2025:10111Red Hat Product SecurityMedium
Red Hat Security Advisory: microcode_ctl security update
- RHSA-2025:10108Red Hat Product SecurityMedium
Red Hat Security Advisory: microcode_ctl security update
- RHSA-2025:10107Red Hat Product SecurityMedium
Red Hat Security Advisory: microcode_ctl security update
- RHSA-2025:10101Red Hat Product SecurityMedium
Red Hat Security Advisory: microcode_ctl security update
- +3 more
Patch Availability(12)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | intel-microcode (3.20250512.0ubuntu0.24.10.1) @ oracular | 2026-05-21 | ubuntu |
| redhat | microcode_ctl-4:20250512-1.el8_10 | 2025-07-14 | redhat |
| redhat | microcode_ctl-4:20191115-4.20250512.1.el8_2 | 2025-07-01 | redhat |
| redhat | microcode_ctl-4:20210216-1.20250512.1.el8_4 | 2025-07-01 | redhat |
| redhat | microcode_ctl-4:20220809-2.20250512.1.el9_2 | 2025-07-01 | redhat |
| redhat | microcode_ctl-4:20230808-2.20250512.1.el9_4 | 2025-07-01 | redhat |
| redhat | microcode_ctl-2:2.1-53.26.el7_7.1 | 2025-07-01 | redhat |
| redhat | microcode_ctl-2:2.1-73.24.el7_9 | 2025-07-01 | redhat |
| redhat | microcode_ctl-4:20220809-2.20250512.1.el8_8 | 2025-07-01 | redhat |
| redhat | microcode_ctl-4:20220207-1.20250512.1.el9_0 | 2025-07-01 | redhat |
| redhat | microcode_ctl-4:20220207-1.20250512.1.el8_6 | 2025-07-01 | redhat |
| redhat | microcode_ctl-4:20250211-1.20250512.1.el9_6 | 2025-06-24 | 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.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 10× in last 7d / 43× 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 115 total refreshes for this CVE.
- 2026-07-22 14:07 UTCEPSS rescore
- 2026-07-22 14:07 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-18 10:03 UTCEPSS rescore
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 01:59 UTCEPSS rescore
- 2026-07-15 01:59 UTCEPSS rescore
- 2026-07-13 22:29 UTCEPSS rescore
- 2026-07-13 22:29 UTCEPSS rescore
- 2026-07-13 06:12 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 05:45 UTCEPSS rescore
- 2026-07-11 08:26 UTCEPSS rescore
- 2026-07-11 08:26 UTCEPSS rescore
- 2026-07-10 12:52 UTCOSV refresh
- 2026-07-09 19:09 UTCEPSS rescore
- 2026-07-08 15:14 UTCEPSS rescore
- 2026-07-07 13:45 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-07-06 16:26 UTCEPSS rescore
- 2026-07-06 02:22 UTCEPSS rescore
- 2026-07-06 02:22 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:30 UTCEPSS rescore
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-06-30 23:21 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:55 UTCEPSS rescore
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 14:04 UTCEPSS rescore
- 2026-06-24 14:04 UTCEPSS rescore
- 2026-06-23 21:32 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-21 22:12 UTCOSV refresh
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-19 19:25 UTCEPSS rescore
- 2026-06-19 19:25 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-17 17:52 UTCEPSS rescore
- 2026-06-16 17:52 UTCEPSS rescore
- 2026-06-15 17:48 UTCEPSS rescore
- 2026-06-14 23:17 UTCEPSS rescore
- 2026-06-13 22:59 UTCEPSS rescore
- 2026-06-13 22:59 UTCEPSS rescore
- 2026-06-12 23:11 UTCEPSS rescore
- 2026-06-11 13:59 UTCEPSS rescore
- 2026-06-10 22:18 UTCEPSS rescore
- 2026-06-10 13:21 UTCEPSS rescore
- 2026-06-08 14:16 UTCEPSS rescore
- 2026-06-08 14:16 UTCEPSS rescore
- 2026-06-07 15:24 UTCEPSS rescore
- 2026-06-06 13:47 UTCEPSS rescore
- 2026-06-06 13:47 UTCEPSS rescore
- 2026-06-05 22:46 UTCEPSS rescore
- 2026-06-05 22:46 UTCEPSS rescore
- 2026-06-05 06:10 UTCEPSS rescore
- 2026-06-05 06:10 UTCEPSS rescore
- 2026-06-03 07:40 UTCOSV refresh
- 2026-06-02 20:12 UTCEPSS rescore
- 2026-06-02 20:12 UTCEPSS rescore
- 2026-06-01 13:51 UTCEPSS rescore
- 2026-06-01 13:51 UTCEPSS rescore
- 2026-05-31 22:30 UTCEPSS rescore
- 2026-05-31 22:30 UTCEPSS rescore
- 2026-05-31 00:16 UTCEPSS rescore
- 2026-05-31 00:16 UTCEPSS rescore
- 2026-05-29 13:44 UTCEPSS rescore
- 2026-05-28 13:44 UTCEPSS rescore
- 2026-05-28 13:44 UTCEPSS rescore
- 2026-05-28 13:44 UTCEPSS rescore
- 2026-05-28 13:44 UTCEPSS rescore
- 2026-05-27 13:40 UTCEPSS rescore
- 2026-05-27 13:40 UTCEPSS rescore
- 2026-05-27 13:40 UTCEPSS rescore
- 2026-05-27 13:40 UTCEPSS rescore
- 2026-05-26 07:18 UTCEPSS rescore
- 2026-05-26 07:18 UTCEPSS rescore
- 2026-05-26 07:18 UTCEPSS rescore
- 2026-05-26 07:18 UTCEPSS rescore
- 2026-05-24 16:56 UTCEPSS rescore
- 2026-05-23 15:20 UTCEPSS rescore
- 2026-05-22 21:16 UTCEPSS rescore
- 2026-05-22 21:16 UTCEPSS rescore
- 2026-05-22 21:16 UTCEPSS rescore
Frequently asked(5)
What is CVE-2025-20012?
When was CVE-2025-20012 disclosed?
Is CVE-2025-20012 actively exploited?
What is the CVSS score of CVE-2025-20012?
How do I remediate CVE-2025-20012?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-20012
Is Your Infrastructure Affected by CVE-2025-20012?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.