x86/mm, kexec, ima: Use memblock_free_late() from ima_free_kexec_buffer()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.1.566.5.66.6In the Linux kernel, the following vulnerability has been resolved:
x86/mm, kexec, ima: Use memblock_free_late() from ima_free_kexec_buffer()
The code calling ima_free_kexec_buffer() runs long after the memblock allocator has already been torn down, potentially resulting in a use after free in memblock_isolate_range().
With KASAN or KFENCE, this use after free will result in a BUG from the idle task, and a subsequent kernel panic.
Switch ima_free_kexec_buffer() over to memblock_free_late() to avoid that bug.
From the CVE record · Linux
In the Linux kernel, ima_free_kexec_buffer() can call the memblock allocator after it has been torn down, causing a use-after-free. With KASAN or KFENCE, this can trigger a BUG from the idle task and a kernel panic. The input does not describe an attacker path, authentication requirements, or user interaction.
Engineers running the Linux kernel should check their kernel version; affected versions are not specified in the input.