efi/capsule-loader: fix incorrect allocation size
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f24c4d478013d82bd1b943df566fff3561d52864 · < 11aabd7487857b8e7d768fefb092f66dfde68492| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
efi/capsule-loader: fix incorrect allocation size
gcc-14 notices that the allocation with sizeof(void) on 32-bit architectures is not enough for a 64-bit phys_addr_t:
drivers/firmware/efi/capsule-loader.c: In function 'efi_capsule_open': drivers/firmware/efi/capsule-loader.c:295:24: error: allocation of insufficient size '4' for type 'phys_addr_t' {aka 'long long unsigned int'} with size '8' [-Werror=alloc-size] 295 | cap_info->phys = kzalloc(sizeof(void *), GFP_KERNEL); | ^
Use the correct type instead here.
From the CVE record · Linux
The Linux kernel’s EFI capsule loader allocates too little space for a 64-bit physical address on 32-bit architectures. The input does not establish what an attacker could do or whether exploitation requires local access, authentication, or user interaction.
Engineers running the Linux kernel on 32-bit architectures should check whether their kernel includes the EFI capsule loader fix; affected versions were not specified.