Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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 ]

Timeline

  1. ID reserved

    By Linux

  2. · 17 days later

    Published

  3. · 21 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-50141, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.25% · top 84% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected cefc7ca46235f01d5233e3abd4b79452af01d9e9 – < 8df52929530839e878e6912e33348b54101e3250
    • affected cefc7ca46235f01d5233e3abd4b79452af01d9e9 – < 8ce081ad842510f0e70fa6065a401660eac876d4
    • affected cefc7ca46235f01d5233e3abd4b79452af01d9e9 – < 795b080d9aa127215a5baf088a22fa09341a0126
    • affected cefc7ca46235f01d5233e3abd4b79452af01d9e9 – < 20e9fafb8bb6f545667d7916b0e81e68c0748810
    • affected cefc7ca46235f01d5233e3abd4b79452af01d9e9 – < 088984c8d54c0053fc4ae606981291d741c5924b

  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 5.15.171 – ≤ 5.15.*
    • unaffected 6.1.115 – ≤ 6.1.*
    • unaffected 6.6.59 – ≤ 6.6.*
    • unaffected 6.11.6 – ≤ 6.11.*
    • unaffected 6.12 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-50141 badge
[![CVE-2024-50141](https://cveledger.app/badge/CVE-2024-50141.svg)](https://cveledger.app/cve/CVE-2024-50141)

Record last updated .