intel-microcode: Improper handling of overlap between protected memory ranges in some microcode for some Intel(R) Processors within Ri...
CVE-2026-20760 is fixed in 3 products on 1 platform, first by DEBIAN-CVE-2026-20760, released August 11, 2026. It is not reported as exploited. Patch Radar priority: Routine.
Improper handling of overlap between protected memory ranges in some microcode for some Intel(R) Processors within Ring 0: Hypervisor may allow an escalation of privilege. Authorized adversary with a privileged user combined with a low complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| intel-microcode · Debian 14 | 3.20260925.1 | DEBIAN-CVE-2026-20760 | Aug 11, 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.