CVE-2025-36920
Out-of-Bounds Write in ARM64 KVM hyp_alloc Enables Privilege Escalation
Publication date: 2026-03-10
Last updated on: 2026-03-11
Assigner: Google Devices
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| android | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
| CWE-20 | The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the hyp_alloc function within the ARM64 KVM hypervisor code, specifically in the file arch/arm64/kvm/hyp/nvhe/alloc.c. It is caused by improper input validation that can lead to an out of bounds write.
An out of bounds write means that the program writes data outside the boundaries of allocated memory, which can corrupt memory and lead to unexpected behavior.
Exploitation of this vulnerability can result in local escalation of privilege without requiring any additional execution privileges or user interaction.
How can this vulnerability impact me? :
This vulnerability can allow an attacker with local access to escalate their privileges on the affected system.
Because no additional execution privileges or user interaction are needed, an attacker who can run code locally could exploit this flaw to gain higher privileges, potentially leading to full control over the system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know