CVE-2026-20901

intel-microcode: Improper input validation for some Intel(R) Xeon(R) processors within firmware may allow an escalation of privilege

CVE-2026-20901 is fixed in 3 products on 1 platform, first by DEBIAN-CVE-2026-20901, released August 11, 2026. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
5.3
medium
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0010
0th percentile

Improper input validation for some Intel(R) Xeon(R) processors within firmware may allow an escalation of privilege. Startup code and smm adversary with a privileged user combined with a high complexity attack may enable data alteration. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (high) and availability (none) impacts.

Where it's fixed

ProductFixed inFixReleased
Linux
intel-microcode · Debian 14 3.20260925.1 DEBIAN-CVE-2026-20901 Aug 11, 2026
microcode_ctl · amzn 2023 2:2.1-53.amzn2023.0.16 ALAS2023-2026-2080 Aug 31, 2026
microcode_ctl · ol 10 4:20260812-1.0.2.el9_8 ELSA-2026-500239 Sep 16, 2026
microcode_ctl · ol 8 4:20260812-1.0.2.el9_8 ELSA-2026-500239 Sep 16, 2026
microcode_ctl · ol 9 4:20260812-1.0.2.el9_8 ELSA-2026-500239 Sep 16, 2026
ucode-intel · opensuse-leap 16.0 20260812-160000.1.1 OPENSUSE-SU-2026:21736-1 Sep 2, 2026
ucode-intel · sles 15.6 20260812-150200.68.1 SUSE-SU-2026:4025-1 Sep 7, 2026
ucode-intel · sles 15.7 20260812-150200.68.1 SUSE-SU-2026:4025-1 Sep 7, 2026
ucode-intel · sles 16.0 20260812-160000.1.1 SUSE-SU-2026:23602-1 Sep 21, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.