<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 01 Oct 2026 20:48:48 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-50141 — ACPI: PRM: Find EFI_MEMORY_RUNTIME block for PRM handler and context</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-50141</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ACPI: PRM: Find EFI_MEMORY_RUNTIME block for PRM handler and context&lt;/p&gt;
&lt;p&gt;PRMT needs to find the correct type of block to translate the PA-VA
mapping for EFI runtime services.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;[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:&lt;/p&gt;
&lt;p&gt;Let PRMT find a block with EFI_MEMORY_RUNTIME for PRM handler and PRM
context.&lt;/p&gt;
&lt;p&gt;If no suitable block is found, a warning message will be printed, but
the procedure continues to manage the next PRM handler.&lt;/p&gt;
&lt;p&gt;However, if the PRM handler is actually called without proper allocation,
it would result in a failure during error handling.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;[ rj…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ACPI: PRM: Find EFI_MEMORY_RUNTIME block for PRM handler and context&lt;/p&gt;
&lt;p&gt;PRMT needs to find the correct type of block to translate the PA-VA
mapping for EFI runtime services.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;[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:&lt;/p&gt;
&lt;p&gt;Let PRMT find a block with EFI_MEMORY_RUNTIME for PRM handler and PRM
context.&lt;/p&gt;
&lt;p&gt;If no suitable block is found, a warning message will be printed, but
the procedure continues to manage the next PRM handler.&lt;/p&gt;
&lt;p&gt;However, if the PRM handler is actually called without proper allocation,
it would result in a failure during error handling.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;[ rj…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-50141</guid>
    </item>
  </channel>
</rss>
