CVE-2025-31648
ucode-intel: Improper handling of values in the microcode flow for
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.
Routine
CVSS
n/a
Low
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0015
4th percentile
Improper handling of values in the microcode flow for
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| intel-microcode · Debian 14 | 3.20260210.1 | DEBIAN-CVE-2025-31648 | Feb 10, 2026 |
| intel-microcode · Ubuntu 18.04.6 LTS (bionic) | 3.20260210.0ubuntu0.18.04.1+esm1 | intel-microcode 3.20260210.0ubuntu0.18.04.1+esm1 | Feb 10, 2026 |
| intel-microcode · Ubuntu 20.04 LTS (focal) | 3.20260210.0ubuntu0.20.04.1+esm1 | intel-microcode 3.20260210.0ubuntu0.20.04.1+esm1 | Feb 10, 2026 |
| intel-microcode · Ubuntu 22.04.1 LTS (jammy) | 3.20260210.0ubuntu0.22.04.1 | intel-microcode 3.20260210.0ubuntu0.22.04.1 | Feb 10, 2026 |
| intel-microcode · Ubuntu 24.04.5 LTS (noble) | 3.20260210.0ubuntu0.24.04.1 | intel-microcode 3.20260210.0ubuntu0.24.04.1 | Feb 10, 2026 |
| intel-microcode · Ubuntu 25.10 (questing) | 3.20260210.0ubuntu0.25.10.1 | intel-microcode 3.20260210.0ubuntu0.25.10.1 | Feb 10, 2026 |
| microcode_ctl · amzn 2023 | 2:2.1-53.amzn2023.0.15 | ALAS2023-2026-1675 | May 11, 2026 |
| ucode-intel · opensuse-leap 15.6 | 20260210-150200.62.1 | SUSE-SU-2026:0668-1 | Feb 26, 2026 |
| ucode-intel · opensuse-leap 16.0 | 20260210-160000.1.1 | OPENSUSE-SU-2026:20401-1 | Mar 19, 2026 |
| ucode-intel · sles 15.6 | 20260210-150200.62.1 | SUSE-SU-2026:0668-1 | Feb 26, 2026 |
| ucode-intel · sles 15.7 | 20260210-150200.62.1 | SUSE-SU-2026:0668-1 | Feb 26, 2026 |
| ucode-intel · sles 16.0 | 20260210-160000.1.1 | SUSE-SU-2026:20941-1 | Mar 19, 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.