intel-microcode: Insufficient control flow management in the Alias Checking Trusted Module(ACTM) firmware for some Intel(R) Xeon(R) pr...
CVE-2025-24305 is fixed in 2 products on 1 platform, first by intel-microcode 3.20250812.0ubuntu0.18.04.1+esm1, released August 12, 2025. It is not reported as exploited. Patch Radar priority: Routine.
Insufficient control flow management in the Alias Checking Trusted Module(ACTM) firmware for some Intel(R) Xeon(R) processors may allow a privilegeduser to potentially enable escalation of privilege via local access.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| intel-microcode · Debian 12.15 (bookworm) | 3.20250812.1~deb12u1 | DEBIAN-CVE-2025-24305 | Aug 12, 2025 |
| intel-microcode · Debian 13.5 (trixie) | 3.20250812.1~deb13u1 | DEBIAN-CVE-2025-24305 | Aug 12, 2025 |
| intel-microcode · Debian 14 | 3.20250812.1 | DEBIAN-CVE-2025-24305 | Aug 12, 2025 |
| intel-microcode · Ubuntu 18.04.6 LTS (bionic) | 3.20250812.0ubuntu0.18.04.1+esm1 | intel-microcode 3.20250812.0ubuntu0.18.04.1+esm1 | Aug 12, 2025 |
| intel-microcode · Ubuntu 20.04 LTS (focal) | 3.20250812.0ubuntu0.20.04.1+esm1 | intel-microcode 3.20250812.0ubuntu0.20.04.1+esm1 | Aug 12, 2025 |
| intel-microcode · Ubuntu 22.04.1 LTS (jammy) | 3.20250812.0ubuntu0.22.04.1 | intel-microcode 3.20250812.0ubuntu0.22.04.1 | Aug 12, 2025 |
| intel-microcode · Ubuntu 24.04.5 LTS (noble) | 3.20250812.0ubuntu0.24.04.1 | intel-microcode 3.20250812.0ubuntu0.24.04.1 | Aug 12, 2025 |
| intel-microcode · Ubuntu 25.04 (plucky) | 3.20250812.0ubuntu0.25.04.1 | intel-microcode 3.20250812.0ubuntu0.25.04.1 | Jan 16, 2026 |
| intel-microcode · Ubuntu 25.10 (questing) | 3.20250812.0ubuntu0.25.10.1 | intel-microcode 3.20250812.0ubuntu0.25.10.1 | Aug 12, 2025 |
| microcode_ctl · amzn 2023 | 2:2.1-53.amzn2023.0.13 | ALAS2023-2025-1190 | Sep 10, 2025 |
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.