Linux
edk2 security updates
Patch Radar has 87 security fixes for edk2, closing 38 CVEs. The newest security fix is RLSA-2026:39297 (0:20251114-5.el10_2.2), released July 15, 2026.
Latest version
n/a
Release date not known
Security fixes
87
On record in Patch Radar
CVEs
38
Closed by those fixes
Exploited
0
Vendor report or CISA KEV
Security fixes, newest first
| Priority | Fix | Release | Fixed in | CVEs | Exploited | Released |
|---|---|---|---|---|---|---|
| High | RLSA-2026:39297 | rocky 10 | 0:20251114-5.el10_2.2 | 2 | Jul 15, 2026 | |
| High | RLSA-2026:36721 | rocky 8 | 0:20220126gitbb1bba3d77-13.el8_10.10 | 1 | Jul 9, 2026 | |
| High | RLSA-2026:18465 | rocky 10 | 0:20251114-5.el10 | 1 | May 29, 2026 | |
| Routine | DEBIAN-CVE-2024-13745 | Debian 14 | 2026.05-3 | 1 | May 29, 2026 | |
| High | RHSA-2026:39297 | RHEL 10 | 20251114-5.el10_2.2 | 2 | Apr 7, 2026 | |
| High | RLSA-2026:2776 | rocky 9 | 0:20241117-4.el9_7.3 | 1 | Feb 24, 2026 | |
| High | DEBIAN-CVE-2025-2296 | Debian 13.5 (trixie) | 2025.02-1 | 1 | Dec 9, 2025 | |
| High | DEBIAN-CVE-2025-2296 | Debian 14 | 2025.02-1 | 1 | Dec 9, 2025 | |
| Routine | DEBIAN-CVE-2024-38798 | Debian 14 | 2025.11-1 | 1 | Dec 9, 2025 | |
| High | RHSA-2026:18465 | RHEL 10 | 20251114-5.el10_2 | 1 | Dec 9, 2025 | |
| High | DEBIAN-CVE-2025-2486 | Debian 12.15 (bookworm) | 2022.11-6+deb12u1 | 1 | Nov 26, 2025 | |
| High | DEBIAN-CVE-2025-2486 | Debian 13.5 (trixie) | 2023.11-7 | 1 | Nov 26, 2025 | |
| High | DEBIAN-CVE-2025-2486 | Debian 14 | 2023.11-7 | 1 | Nov 26, 2025 | |
| High | RHSA-2026:65132 | RHEL 10 | 20241117-2.el10_0.2 | 1 | Sep 30, 2025 | |
| Routine | DEBIAN-CVE-2024-38805 | Debian 13.5 (trixie) | 2025.02-8+deb13u1 | 1 | Aug 12, 2025 | |
| Routine | DEBIAN-CVE-2024-38805 | Debian 14 | 2025.02-9 | 1 | Aug 12, 2025 | |
| High | DEBIAN-CVE-2025-3770 | Debian 13.5 (trixie) | 2025.02-8+deb13u1 | 1 | Aug 7, 2025 | |
| High | DEBIAN-CVE-2025-3770 | Debian 14 | 2025.02-9 | 1 | Aug 7, 2025 | |
| Routine | RLSA-2024:11185 | rocky 8 | 0:20220126gitbb1bba3d77-13.el8_10.4 | 1 | Jun 24, 2025 | |
| Routine | DLA-4207-1 | Debian 11.6 (bullseye) | 2020.11-2+deb11u3 | 1 | Jun 2, 2025 | |
| High | RLSA-2024:3017 | rocky 8 | 0:20220126gitbb1bba3d77-13.el8_10 | 8 | May 7, 2025 | |
| High | RLSA-2024:5297 | rocky 8 | 0:20220126gitbb1bba3d77-13.el8_10.2 | 3 | May 7, 2025 | |
| Routine | DEBIAN-CVE-2024-38797 | Debian 13.5 (trixie) | 2025.02-8 | 1 | Apr 7, 2025 | |
| Routine | DEBIAN-CVE-2024-38797 | Debian 14 | 2025.02-8 | 1 | Apr 7, 2025 | |
| High | RLSA-2024:9088 | rocky 9 | 0:20240524-6.el9_5.3 | 4 | Mar 17, 2025 | |
| Routine | RLSA-2024:11219 | rocky 9 | 0:20240524-6.el9_5.3 | 1 | Mar 17, 2025 | |
| Routine | DEBIAN-CVE-2025-2295 | Debian 13.5 (trixie) | 2025.02-4 | 1 | Mar 14, 2025 | |
| Routine | DEBIAN-CVE-2025-2295 | Debian 14 | 2025.02-4 | 1 | Mar 14, 2025 | |
| Routine | DEBIAN-CVE-2024-13176 | Debian 13.5 (trixie) | 2025.02-8+deb13u1 | 1 | Jan 20, 2025 | |
| Routine | DEBIAN-CVE-2024-13176 | Debian 14 | 2025.02-9 | 1 | Jan 20, 2025 | |
| High | RLSA-2024:8935 | rocky 9 | 0:20231122-6.el9_4.4 | 1 | Nov 8, 2024 | |
| Routine | DEBIAN-CVE-2024-38796 | Debian 12.15 (bookworm) | 2022.11-6+deb12u2 | 1 | Sep 27, 2024 | |
| Routine | DEBIAN-CVE-2024-38796 | Debian 13.5 (trixie) | 2024.08-3 | 1 | Sep 27, 2024 | |
| Routine | DEBIAN-CVE-2024-38796 | Debian 14 | 2024.08-3 | 1 | Sep 27, 2024 | |
| High | DEBIAN-CVE-2024-1298 | Debian 12.15 (bookworm) | 2022.11-6+deb12u2 | 1 | May 30, 2024 | |
| High | DEBIAN-CVE-2024-1298 | Debian 13.5 (trixie) | 2024.05-1 | 1 | May 30, 2024 | |
| High | DEBIAN-CVE-2024-1298 | Debian 14 | 2024.05-1 | 1 | May 30, 2024 | |
| High | RLSA-2024:2264 | rocky 9 | 0:20231122-6.el9 | 8 | May 10, 2024 | |
| High | RLSA-2024:1063 | rocky 8 | 0:20220126gitbb1bba3d77-6.el8_9.6 | 2 | Mar 12, 2024 | |
| Routine | DEBIAN-CVE-2023-48733 | Debian 13.5 (trixie) | 2023.11-7 | 1 | Feb 14, 2024 | |
| Routine | DEBIAN-CVE-2023-48733 | Debian 14 | 2023.11-7 | 1 | Feb 14, 2024 | |
| Routine | DSA-5624-1 | Debian 11.6 (bullseye) | 2020.11-2+deb11u2 | 1 | Feb 14, 2024 | |
| Routine | DSA-5624-1 | Debian 12.15 (bookworm) | 2022.11-6+deb12u1 | 1 | Feb 14, 2024 | |
| High | DEBIAN-CVE-2023-45237 | Debian 14 | 2024.05-1 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45237 | Debian 13.5 (trixie) | 2024.05-1 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45233 | Debian 12.15 (bookworm) | 2022.11-6+deb12u1 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45233 | Debian 13.5 (trixie) | 2023.11-6 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45233 | Debian 14 | 2023.11-6 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45232 | Debian 12.15 (bookworm) | 2022.11-6+deb12u1 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45232 | Debian 13.5 (trixie) | 2023.11-6 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45232 | Debian 14 | 2023.11-6 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45235 | Debian 12.15 (bookworm) | 2022.11-6+deb12u1 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45235 | Debian 13.5 (trixie) | 2023.11-6 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45235 | Debian 14 | 2023.11-6 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45234 | Debian 12.15 (bookworm) | 2022.11-6+deb12u1 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45234 | Debian 13.5 (trixie) | 2023.11-6 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45234 | Debian 14 | 2023.11-6 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45236 | Debian 14 | 2024.05-1 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45236 | Debian 13.5 (trixie) | 2024.05-1 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45230 | Debian 14 | 2023.11-6 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45230 | Debian 12.15 (bookworm) | 2022.11-6+deb12u1 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45230 | Debian 13.5 (trixie) | 2023.11-6 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45229 | Debian 12.15 (bookworm) | 2022.11-6+deb12u1 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45229 | Debian 13.5 (trixie) | 2023.11-6 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45229 | Debian 14 | 2023.11-6 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45231 | Debian 12.15 (bookworm) | 2022.11-6+deb12u1 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45231 | Debian 13.5 (trixie) | 2023.11-6 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2023-45231 | Debian 14 | 2023.11-6 | 1 | Jan 16, 2024 | |
| High | DEBIAN-CVE-2022-36763 | Debian 12.15 (bookworm) | 2022.11-6+deb12u1 | 1 | Jan 9, 2024 | |
| High | DEBIAN-CVE-2022-36763 | Debian 13.5 (trixie) | 2023.11-5 | 1 | Jan 9, 2024 | |
| High | DEBIAN-CVE-2022-36763 | Debian 14 | 2023.11-5 | 1 | Jan 9, 2024 | |
| High | DEBIAN-CVE-2022-36765 | Debian 12.15 (bookworm) | 2022.11-6+deb12u1 | 1 | Jan 9, 2024 | |
| High | DEBIAN-CVE-2022-36765 | Debian 13.5 (trixie) | 2023.11-5 | 1 | Jan 9, 2024 | |
| High | DEBIAN-CVE-2022-36765 | Debian 14 | 2023.11-5 | 1 | Jan 9, 2024 | |
| High | DEBIAN-CVE-2022-36764 | Debian 12.15 (bookworm) | 2022.11-6+deb12u1 | 1 | Jan 9, 2024 | |
| High | DEBIAN-CVE-2022-36764 | Debian 13.5 (trixie) | 2023.11-5 | 1 | Jan 9, 2024 | |
| High | DEBIAN-CVE-2022-36764 | Debian 14 | 2023.11-5 | 1 | Jan 9, 2024 | |
| High | DEBIAN-CVE-2021-38578 | Debian 12.15 (bookworm) | 2022.11-1 | 1 | Mar 3, 2022 | |
| High | DEBIAN-CVE-2021-38578 | Debian 13.5 (trixie) | 2022.11-1 | 1 | Mar 3, 2022 | |
| High | DEBIAN-CVE-2021-38578 | Debian 14 | 2022.11-1 | 1 | Mar 3, 2022 | |
| High | DEBIAN-CVE-2021-38576 | Debian 12.15 (bookworm) | 2021.11-1 | 1 | Jan 3, 2022 | |
| High | DEBIAN-CVE-2021-38576 | Debian 13.5 (trixie) | 2021.11-1 | 1 | Jan 3, 2022 | |
| High | DEBIAN-CVE-2021-38576 | Debian 14 | 2021.11-1 | 1 | Jan 3, 2022 | |
| High | DEBIAN-CVE-2021-38575 | Debian 12.15 (bookworm) | 2021.08-1 | 1 | Dec 1, 2021 | |
| High | DEBIAN-CVE-2021-38575 | Debian 13.5 (trixie) | 2021.08-1 | 1 | Dec 1, 2021 | |
| High | DEBIAN-CVE-2021-38575 | Debian 14 | 2021.08-1 | 1 | Dec 1, 2021 | |
| High | RLSA-2021:4198 | rocky 8 | 0:20210527gite1999b264f1f-3.el8 | 2 | Nov 9, 2021 |
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.