ima: verify the previous kernel's IMA buffer lies in addressable RAM
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b69a2afd5afce9bf6d56e349d6ab592c916e20f2 · < 10d1c75ed4382a8e79874379caa2ead8952734f9| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ima: verify the previous kernel's IMA buffer lies in addressable RAM
Patch series "Address page fault in ima_restore_measurement_list()", v3.
When the second-stage kernel is booted via kexec with a limiting command line such as "mem=<size>" we observe a pafe fault that happens.
BUG: unable to handle page fault for address: ffff97793ff47000 RIP: ima_restore_measurement_list+0xdc/0x45a #PF: error_code(0x0000) not-present page
This happens on x86_64 only, as this is already fixed in aarch64 in commit: cbf9c4b9617b ("of: check previous kernel's ima-kexec-buffer against memory bounds")
This patch (of 3):
When the second-stage kernel is booted with a limiting command line (e.g. "mem=<size>"), the IMA measurement buffer handed over from the previous kernel may fall outside the addressable RAM of the new kernel. Accessing such a buffer can fault during early restore.
From the CVE record · Linux
On x86_64, a second-stage kernel booted via kexec with a limiting command line such as mem=<size> can fault while restoring the previous kernel's IMA measurement buffer if that buffer falls outside addressable RAM. The input does not describe an attacker path, authentication requirement, or user interaction.
Engineers running the Linux kernel on x86_64 with kexec and IMA measurement restore should check their systems; affected versions were not specified.