CVE-2025-22413

CVE-2025-22413 is a medium-severity vulnerability in Google Android with a CVSS 3.x base score of 4.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-703.

Key facts

Description

In multiple functions of hyp-main.c, there is a possible privilege escalation due to a logic error in the code. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

Frequently asked questions

What is CVE-2025-22413?
In multiple functions of hyp-main.c, there is a possible privilege escalation due to a logic error in the code. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
How severe is CVE-2025-22413?
CVE-2025-22413 has a CVSS 3.x base score of 4.0, rated medium severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2025-22413 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-22413?
CVE-2025-22413 affects Google Android. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-22413?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-22413 have an EU (EUVD) identifier?
Yes. CVE-2025-22413 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-25840.
When was CVE-2025-22413 published?
CVE-2025-22413 was published on 2025-08-26 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Google Android

All CVEs affecting Google Android →

Other CWE-703 vulnerabilities

Browse all CWE-703 vulnerabilities →