Resource Injection Affecting kernel-rt-debug-modules-core package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RHEL9-KERNELRTDEBUGMODULESCORE-8425801
- published27 Nov 2024
- disclosed7 Nov 2024
Introduced: 7 Nov 2024
NewCVE-2024-50141 (opens in a new tab)How to fix?
There is no fixed version for RHEL:9 kernel-rt-debug-modules-core.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-rt-debug-modules-core package and not the kernel-rt-debug-modules-core package as distributed by RHEL.
See How to fix? for RHEL:9 relevant fixed versions and status.
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 ]
References
- https://access.redhat.com/security/cve/CVE-2024-50141
- https://git.kernel.org/stable/c/088984c8d54c0053fc4ae606981291d741c5924b
- https://git.kernel.org/stable/c/20e9fafb8bb6f545667d7916b0e81e68c0748810
- https://git.kernel.org/stable/c/795b080d9aa127215a5baf088a22fa09341a0126
- https://git.kernel.org/stable/c/8ce081ad842510f0e70fa6065a401660eac876d4
- https://git.kernel.org/stable/c/8df52929530839e878e6912e33348b54101e3250