medium
5.5
Advisory Published
Updated

CVE-2024-50141: ACPI: PRM: Find EFI_MEMORY_RUNTIME block for PRM handler and context

First published: Thu Nov 07 2024(Updated: )

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 ]

Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Affected SoftwareAffected VersionHow to fix
Linux Kernel>=5.14<5.15.171
Linux Kernel>=5.16<6.1.115
Linux Kernel>=6.2<6.6.59
Linux Kernel>=6.7<6.11.6
Linux Kernel=6.12-rc1
Linux Kernel=6.12-rc2
Linux Kernel=6.12-rc3
Linux Kernel=6.12-rc4
debian/linux
5.10.223-1
5.10.226-1
6.1.123-1
6.1.128-1
6.12.12-1
6.12.15-1
debian/linux-6.1
6.1.119-1~deb11u1

Remedy

https://git.kernel.org/stable/c/088984c8d54c0053fc4ae606981291d741c5924b

Remedy

https://git.kernel.org/stable/c/20e9fafb8bb6f545667d7916b0e81e68c0748810

Remedy

https://git.kernel.org/stable/c/795b080d9aa127215a5baf088a22fa09341a0126

Remedy

https://git.kernel.org/stable/c/8ce081ad842510f0e70fa6065a401660eac876d4

Remedy

https://git.kernel.org/stable/c/8df52929530839e878e6912e33348b54101e3250

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2024-50141?

    CVE-2024-50141 has a medium severity rating due to its potential impact on kernel operations.

  • How do I fix CVE-2024-50141?

    To fix CVE-2024-50141, update your Linux kernel to a version that addresses this vulnerability.

  • Which versions of the Linux kernel are affected by CVE-2024-50141?

    CVE-2024-50141 affects multiple Linux kernel versions, specifically those between 5.14 and 5.15.171, among others up to 6.12-rc4.

  • What is the impact of CVE-2024-50141?

    The impact of CVE-2024-50141 may involve incorrect access to EFI runtime services, potentially leading to system instability.

  • Is CVE-2024-50141 publicly known?

    Yes, CVE-2024-50141 is publicly documented and can be referenced in security advisories and vulnerability databases.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203