Skip to main content
Mallory
UnratedPublic exploitVulnerability

CVE-2026-17588: Missing Timer Reentrancy Guards in QEMU xHCI Emulation

Updated 27 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-17588CWE-1265

CVE-2026-17588 is a reentrancy vulnerability in QEMU's emulated xHCI USB host controller. Timer functions lack reentrancy guards, allowing unintended reentrant execution. The upstream correction adds guards to these functions. The vulnerability is classified as locally exploitable with potentially high confidentiality, integrity, and availability impacts; the precise triggering sequence and resulting failure mechanism are not established.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A local authenticated attacker with low privileges may compromise the confidentiality, integrity, and availability of an affected system. Amazon Linux assigns CVSS v3.1 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Specific consequences such as arbitrary code execution or virtual-machine escape are not established for this CVE.

Mitigation

If you can’t patch tonight, do this now.

Until a fixed package is available, restrict local interactive access and privileges, limit access to QEMU virtual-machine management, and restrict USB emulation and passthrough features. These are exposure-reduction measures rather than a confirmed complete workaround.

Remediation

Patch, then assume compromise.

Install a vendor-supported QEMU update incorporating the xHCI timer reentrancy guards. Amazon Linux 2023 advisory ALAS2023-2026-3241 includes this CVE and recommends updating QEMU using release 2023.12.20261026. Earlier package-status information lists Amazon Linux 2 and Amazon Linux 2023 QEMU fixes as pending; verify current package availability and fixed-version status before deployment.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
qemu-xhci-complete-uafThis standalone repository contains a Python proof of concept and a Docker-based QEMU reproduction lab, not a framework module. Its 10 files comprise two Python programs, two Bash scripts, a Dockerfile, Compose configuration, two ignore files, a README, and an AGPLv3 license. The root Python entry point mainly prints a banner and invokes lab/run.sh. That runner builds and starts the container, waits for qtest, executes lab/poc.py, records output, and tears down the Compose environment. The Dockerfile fetches and builds the claimed QEMU revision with AddressSanitizer; entrypoint.sh configures the emulated USB/UAS devices and diagnostic tracing. The visible reproducer sequence discovers and maps xHCI, initializes the controller, addresses/configures the USB device and bulk endpoints, queues status input, redirects the event-ring destination to the doorbell BAR, queues a disable-slot command, and initiates a UAS operation. The claimed flaw is that asynchronous xhci_complete event DMA occurs without the xHCI memory-reentrancy guard. A doorbell write can therefore reenter xhci_process_commands and free the transfer still referenced by the outer completion callback. This supports a memory-corruption/crash proof of concept, not a demonstrated guest-to-host code-execution chain. TCP is used for local lab instrumentation rather than as the underlying vulnerability's remote attack vector. The README explicitly distinguishes this allegedly unassigned vulnerability from the related, reportedly patched CVE-2026-17588 timer path; CVE-2021-3713 is also only a comparison, not a demonstrated target. Target-version availability, revision validity, and reported sanitizer success were not independently verified. The central portion of lab/poc.py is truncated, limiting validation of protocol details and success criteria; the visible tail allows a fallback success description beyond an explicit sanitizer report. No malicious downloader, credential theft, or exfiltration behavior is apparent in the supplied code. Repository ref and archive size were not supplied; the empty ref and zero size are placeholders, not measured values.abraxas · Disclosed Oct 17, 2026 · python · bash · local · hypervisorPoC
FAQ

Frequently asked questions

Is CVE-2026-17588 exploited in the wild?
As of Oct 25, 2026, Mallory has no reports of CVE-2026-17588 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-17588?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-17588, the earliest disclosed Oct 17, 2026.
Is there a patch for CVE-2026-17588?
Install a vendor-supported QEMU update incorporating the xHCI timer reentrancy guards. Amazon Linux 2023 advisory ALAS2023-2026-3241 includes this CVE and recommends updating QEMU using release 2023.12.20261026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.