# CVE-2026-64183 — Linux

> As of 2026-07-19, CVE-2026-64183 is a vulnerability in Linux. No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-64183 as of 2026-07-19; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-07-19

## What is CVE-2026-64183?

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 efisubsys_init() executes, which is where the workqueue is allocated, leading to NULL pointer dereferences. Since acpi_init() [which triggers the early PRM accesses] executes as a subsys_initcall() as well, and has its own dependencies that may be sensitive to initcall ordering, deferring acpi_init() 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 subsys_initcall() level.

1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 78 days ago.

## Severity and exploitation probability

- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Published:** 2026-07-19

## Is CVE-2026-64183 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [Linux](https://intel.threadlinqs.com/vendors/linux): Linux

## How to fix CVE-2026-64183

No vendor patch reference has been recorded for CVE-2026-64183 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-64183

No threat campaign in the Threadlinqs corpus currently references CVE-2026-64183, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD. Last verified by Threadlinqs on 2026-07-21. This product uses the NVD API but is not endorsed or certified by the NVD.

**Other references**

- [git.kernel.org](https://git.kernel.org/stable/c/29cd94e678fcb3c4fd0f359deeac6d61334323fc)
- [git.kernel.org (6996e954ae830f5b793ba6cf449885ca519dbdd2)](https://git.kernel.org/stable/c/6996e954ae830f5b793ba6cf449885ca519dbdd2)
- [git.kernel.org (c32a1fbe0f9a48453a552bb315cc4f1e7a74084e)](https://git.kernel.org/stable/c/c32a1fbe0f9a48453a552bb315cc4f1e7a74084e)
- [git.kernel.org (e871549f7894ad4114b3dd53f241aa25a268ba8b)](https://git.kernel.org/stable/c/e871549f7894ad4114b3dd53f241aa25a268ba8b)
- [git.kernel.org (13c6da02e767152c9ac4330962247a5e47011035)](https://git.kernel.org/stable/c/13c6da02e767152c9ac4330962247a5e47011035)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-64183
Full detection coverage and IOCs for threats exploiting CVE-2026-64183 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp