CVE-2026-23352
Last modified
CVE-2026-23352 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: x86/efi: defer freeing of boot services memory efi_free_boot_services() frees memory occupied by EFI_BOOT_SERVICES_CODE and EFI_BOOT_SERVICES_DATA using memblock_free_late(). There are two issue with that: memblock_free_late() should be used for memory allocated with memblock_alloc() while the memory reserved with memblock_reserve() should be freed with free_reserved_area(). More acutely, with CONFIG_DEFERRED_STRUCT_PAGE_INIT=y efi_free_boot_services() is called before deferred initialization of the memory map is complete. Benjamin Herrenschmidt reports that this causes a leak of ~140MB of RAM on EC2 t3a.nano instances which only have 512MB or RAM. If the freed memory resides in the areas that memory map for them is still uninitialized, they won't be actually freed because memblock_free_late() calls memblock_free_pages() and the latter skips uninitialized pages. Using free_reserved_area() at this point is also problematic because __free_page() accesses the buddy of the freed page and that again might end up in uninitialized part of the memory map. Delaying the entire efi_free_boot_services() could be problematic because in addition to freeing boot services memory it updates efi.memmap without any synchronization and that's undesirable late in boot when there is concurrency. More robust approach is to only defer freeing of the EFI boot services memory. Split efi_free_boot_services() in two. First efi_unmap_boot_services() collects ranges that should be freed into an array then efi_free_boot_services() later frees them after deferred init is complete.. EPSS estimates a 0.13% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: x86/efi: defer freeing of boot services memory efi_free_boot_services() frees memory occupied by EFI_BOOT_SERVICES_CODE and EFI_BOOT_SERVICES_DATA using memblock_free_late(). There are two issue with that: memblock_free_late() should be used for memory allocated with memblock_alloc() while the memory reserved with memblock_reserve() should be freed with free_reserved_area(). More acutely, with CONFIG_DEFERRED_STRUCT_PAGE_INIT=y efi_free_boot_services() is called before deferred initialization of the memory map is complete. Benjamin Herrenschmidt reports that this causes a leak of ~140MB of RAM on EC2 t3a.nano instances which only have 512MB or RAM. If the freed memory resides in the areas that memory map for them is still uninitialized, they won't be actually freed because memblock_free_late() calls memblock_free_pages() and the latter skips uninitialized pages. Using free_reserved_area() at this point is also problematic because __free_page() accesses the buddy of the freed page and that again might end up in uninitialized part of the memory map. Delaying the entire efi_free_boot_services() could be problematic because in addition to freeing boot services memory it updates efi.memmap without any synchronization and that's undesirable late in boot when there is concurrency. More robust approach is to only defer freeing of the EFI boot services memory. Split efi_free_boot_services() in two. First efi_unmap_boot_services() collects ranges that should be freed into an array then efi_free_boot_services() later frees them after deferred init is complete.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 3.0.1, < 5.10.253 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.203 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.167 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.130 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.77 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.17 | — |
| Linux | Linux Kernel | >= 6.19, < 6.19.7 | — |
| Linux | Linux Kernel | 2.6.39.1 | — |
| Linux | Linux Kernel | 3.0 | — |
| Linux | Linux Kernel | 7.0 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-23352?
How severe is CVE-2026-23352?
How do I fix CVE-2026-23352?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-23346In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23347In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23348In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-23349In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23350In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-23351In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-23353In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23354In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-23355In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23356In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23357In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23358In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-23352?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
