# CVE-2025-31648: ucode-intel: This update for ucode-intel fixes the following issues:  - Intel CPU Microcode was updated to the 20260210 release (b...

CVE-2025-31648 is fixed in 3 products on 1 platform, first by intel-microcode 3.20260210.0ubuntu0.18.04.1+esm1, released February 10, 2026. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2025-31648
- Priority: Routine
- CVSS: n/a (Low)
- EPSS: 0.0015
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Feb 10, 2026

## Description

This update for ucode-intel fixes the following issues:  - Intel CPU Microcode was updated to the 20260210 release (bsc#1258046) - CVE-2024-24853: Updated fix for incorrect behavior order in transition   between executive monitor and SMI transfer monitor (STM) in some Intel(R)   Processor may allow a privileged user to potentially enable escalation   of privilege via local access. (bsc#1229129) - CVE-2025-31648: Improper handling of values in the microcode flow for   some Intel Processor Family may allow an escalation of privilege. (bsc#1258046)

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | intel-microcode Debian 14 | 3.20260210.1 | [DEBIAN-CVE-2025-31648](https://patchblox.com/security/data/fix/linux/debian-cve-2025-31648.md) | Feb 10, 2026 |
| Linux | intel-microcode Ubuntu 18.04.6 LTS (bionic) | 3.20260210.0ubuntu0.18.04.1+esm1 | [intel-microcode 3.20260210.0ubuntu0.18.04.1+esm1](https://patchblox.com/security/data/fix/linux/ubuntu-bionic-intel-microcode-3.20260210.0ubuntu0.18.04.1-esm1.md) | Feb 10, 2026 |
| Linux | intel-microcode Ubuntu 20.04 LTS (focal) | 3.20260210.0ubuntu0.20.04.1+esm1 | [intel-microcode 3.20260210.0ubuntu0.20.04.1+esm1](https://patchblox.com/security/data/fix/linux/ubuntu-focal-intel-microcode-3.20260210.0ubuntu0.20.04.1-esm1.md) | Feb 10, 2026 |
| Linux | intel-microcode Ubuntu 22.04.1 LTS (jammy) | 3.20260210.0ubuntu0.22.04.1 | [intel-microcode 3.20260210.0ubuntu0.22.04.1](https://patchblox.com/security/data/fix/linux/ubuntu-jammy-intel-microcode-3.20260210.0ubuntu0.22.04.1.md) | Feb 10, 2026 |
| Linux | intel-microcode Ubuntu 24.04.5 LTS (noble) | 3.20260210.0ubuntu0.24.04.1 | [intel-microcode 3.20260210.0ubuntu0.24.04.1](https://patchblox.com/security/data/fix/linux/ubuntu-noble-intel-microcode-3.20260210.0ubuntu0.24.04.1.md) | Feb 10, 2026 |
| Linux | intel-microcode Ubuntu 25.10 (questing) | 3.20260210.0ubuntu0.25.10.1 | [intel-microcode 3.20260210.0ubuntu0.25.10.1](https://patchblox.com/security/data/fix/linux/ubuntu-questing-intel-microcode-3.20260210.0ubuntu0.25.10.1.md) | Feb 10, 2026 |
| Linux | microcode_ctl amzn 2023 | 2:2.1-53.amzn2023.0.15 | [ALAS2023-2026-1675](https://patchblox.com/security/data/fix/linux/alas2023-2026-1675.md) | May 11, 2026 |
| Linux | ucode-intel opensuse-leap 15.6 | 20260210-150200.62.1 | [SUSE-SU-2026:0668-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-0668-1.md) | Feb 26, 2026 |
| Linux | ucode-intel opensuse-leap 16.0 | 20260210-160000.1.1 | [OPENSUSE-SU-2026:20401-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20401-1.md) | Mar 19, 2026 |
| Linux | ucode-intel sles 15.6 | 20260210-150200.62.1 | [SUSE-SU-2026:0668-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-0668-1.md) | Feb 26, 2026 |
| Linux | ucode-intel sles 15.7 | 20260210-150200.62.1 | [SUSE-SU-2026:0668-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-0668-1.md) | Feb 26, 2026 |
| Linux | ucode-intel sles 16.0 | 20260210-160000.1.1 | [SUSE-SU-2026:20941-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20941-1.md) | Mar 19, 2026 |

---

Data as of 2026-11-09T07:25:28Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

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.