CVE-2026-64183: efi: Allocate runtime workqueue before ACPI init
In the Linux kernel, the following vulnerability has been resolved:
efi: Allocate runtime workqueue before ACPI init
Since commit
5894cf571e14 ("acpi/prmt: Use EFI runtime sandbox to invoke PRM handlers")
ACPI PRM calls are delegated to a workqueue which runs in a kernel thread, making it easier to detect and mitigate faulting memory accesses performed by the firmware.
Rafael reports that such PRM accesses may occur before efisubsysinit() executes, which is where the workqueue is allocated, leading to NULL pointer dereferences. Since acpiinit() [which triggers the early PRM accesses] executes as a subsysinitcall() as well, and has its own dependencies that may be sensitive to initcall ordering, deferring acpiinit() is not an option.
So instead, split off the workqueue allocation into its own postcore initcall, as this is the only missing piece to allow EFI runtime calls to be made. This ensures that EFI runtime call (including PRM calls) are accessible to all code running at subsysinitcall() level.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch 5894cf571e14
Event History
Frequently Asked Questions
What is the severity of CVE-2026-64183?
CVE-2026-64183 has a risk rating of 17.
How do I fix CVE-2026-64183?
To fix CVE-2026-64183, update to the latest version of the Linux kernel that addresses this vulnerability.
What systems are affected by CVE-2026-64183?
CVE-2026-64183 affects systems running the vulnerable versions of the Linux kernel.
What type of vulnerability is CVE-2026-64183?
CVE-2026-64183 is related to improper timing in the allocation of runtime workqueues before ACPI initialization.
What is the impact of CVE-2026-64183?
The impact of CVE-2026-64183 may involve potential instability or failures in the ACPI operations of affected Linux systems.