CVE-2022-50159
BaseFortify
Publication date: 2025-06-18
Last updated on: 2025-11-25
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's handling of the ima-kexec-buffer from a previous kernel during a kexec operation. Specifically, the function ima_get_kexec_buffer() does not verify whether the previous kernel's ima-kexec-buffer lies within the valid addressable memory range. If the new kernel is booted with a memory limit argument (mem=X) and the previous kernel allocated the ima-kexec-buffer beyond this range, it can cause the kernel to panic due to accessing invalid memory. The fix involves checking the buffer's page frame number range with page_is_ram() to ensure it is within correct memory bounds.
How can this vulnerability impact me? :
This vulnerability can cause a kernel panic when booting a new kernel using kexec if the previous kernel's ima-kexec-buffer is outside the allowed memory range. A kernel panic leads to a system crash, causing downtime and potential data loss or service interruption.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing kernel panic messages related to the ima-kexec-buffer when booting a new kernel with the 'mem=X' argument. Specifically, look for kernel panic logs containing messages like 'BUG: Unable to handle kernel data access on read' and traces involving ima_restore_measurement_list and ima_load_kexec_buffer. A command to reproduce or detect the issue is: sudo kexec --initrd initrd vmlinux --append='mem=16G'. Monitoring system logs (e.g., dmesg or journalctl) for such panic messages after kexec operations can help detect the vulnerability.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version where the issue is fixed. The fix involves checking the returned PFN range of the previous kernel's ima-kexec-buffer with page_is_ram() to ensure it lies within correct memory bounds, preventing kernel panic. Avoid booting new kernels with 'mem=X' arguments that could trigger the issue until the patch is applied.