In multiple locations, there is a possible memory corruption due to a race condition.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The checked facts give no workaround. No mitigation is stated in the sources, so none should be assumed until the vendor publishes one.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 5/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In multiple locations, there is a possible memory corruption due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
What to do
Workaround: The checked facts give no workaround. No mitigation is stated in the sources, so none should be assumed until the vendor publishes one.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Google Android
Version range not reported
Evidence 12
- Link
- Link
- Link
- Link
- Link
Show all 12 sourcesShow fewer sources
- Link
- Link
- Link
- Link
- Link
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-59045
What does this mean?
The bug is a race condition in Android's pvmfw (protected VM firmware) code that can cause memory corruption. When a VMM marks more than one protected vCPU runnable, the vCPUs race to claim the pvmfw primary slot. A rollback of a failed CPU_ON on another CPU can also move a vCPU's power state from ON_PENDING to OFF while a reset is in progress. The race lets the VMM make pvmfw run a second time with its own inputs, and the related WARN path can lead to a host denial of service via hyp_panic.Source: android.googlesource.com, android.googlesource.com
Am I affected, and how do I check?
The checked facts list no affected version ranges. The affected setup involves a VMM that runs protected vCPUs and marks more than one of them runnable, or that hits a CPU_ON failure during reset. To check a device, compare its Android security patch level against the vendor's advisory for CVE-2026-59045.Source: android.googlesource.com, android.googlesource.com
What should I do about it?
The checked facts name no fixed version or upgrade target. Watch the Android security bulletin for a patch that references CVE-2026-59045 and install it when it is released.Source: android.googlesource.com, android.googlesource.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
The checked facts give no workaround. No mitigation is stated in the sources, so none should be assumed until the vendor publishes one.Source: android.googlesource.com, android.googlesource.com