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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: 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.
- 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 __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
Workaround: 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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Google Android
Version range not reported
Evidence 3
- Link
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-59046
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: android.googlesource.com
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: android.googlesource.com
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: 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. 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: android.googlesource.com