CVE-2024-50141

published 7 Nov 2024 · updated 5 Aug 2026

ACPI: PRM: Find EFI_MEMORY_RUNTIME block for PRM handler and context

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 088984c8d54c0053fc4ae606981291d741c5924b, Kernel 20e9fafb8bb6f545667d7916b0e81e68c0748810, Kernel 795b080d9aa127215a5baf088a22fa09341a0126 and 2 more.

In the Linux kernel, the following vulnerability has been resolved: ACPI: PRM: Find EFI_MEMORY_RUNTIME block for PRM handler and context PRMT needs to find the correct type of block to translate the PA-VA mapping for EFI runtime services. The issue arises because the PRMT is finding a block of type EFI_CONVENTIONAL_MEMORY, which is not appropriate for runtime services as described in Section 2.2.2 (Runtime Services) of the UEFI Specification [1]. Since the PRM handler is a type of runtime service, this causes an exception when the PRM handler is called. [Firmware Bug]: Unable to handle paging request in EFI runtime service WARNING: CPU: 22 PID: 4330 at drivers/firmware/efi/runtime-wrappers.c:341 __efi_queue_work+0x11c/0x170 Call trace: Let PRMT find a block with EFI_MEMORY_RUNTIME for PRM handler and PRM context. If no suitable block is found, a warning message will be printed, but the procedure continues to manage the next PRM handler. However, if the PRM handler is actually called without proper allocation, it would result in a failure during error handling. By using the correct memory types for runtime services, ensure that the PRM handler and the context are properly mapped in the virtual address space during runtime, preventing the paging request error. The issue is really that only memory that has been remapped for runtime by the firmware can be used by the PRM handler, and so the region needs to have the EFI_MEMORY_RUNTIME attribute. [ rjw: Subject and changelog edits ]

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=5.14, >=cefc7ca46235f01d5233e3abd4b79452af01d9e9 <088984c8d54c0053fc4ae606981291d741c5924b, >=cefc7ca46235f01d5233e3abd4b79452af01d9e9 <20e9fafb8bb6f545667d7916b0e81e68c0748810, >=cefc7ca46235f01d5233e3abd4b79452af01d9e9 <795b080d9aa127215a5baf088a22fa09341a0126, >=cefc7ca46235f01d5233e3abd4b79452af01d9e9 <8ce081ad842510f0e70fa6065a401660eac876d4, >=cefc7ca46235f01d5233e3abd4b79452af01d9e9 <8df52929530839e878e6912e33348b54101e3250088984c8d54c0053fc4ae606981291d741c5924b, 20e9fafb8bb6f545667d7916b0e81e68c0748810, 795b080d9aa127215a5baf088a22fa09341a0126, 8ce081ad842510f0e70fa6065a401660eac876d4, 8df52929530839e878e6912e33348b54101e3250

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2024-50141 severity on Zeptric[![CVE-2024-50141](https://zeptric.io/badge/cve/CVE-2024-50141.svg)](https://zeptric.io/cve/CVE-2024-50141)