CVE-2025-36922

Unknown Unknown - Not Provided

BaseFortify

Publication date: 2025-12-11

Last updated on: 2025-12-12

Assigner: Google Devices

Description

In bigo_map of bigo_iommu.c, there is a possible information disclosure due to a use after free. This could lead to local escalation of privilege in the OS Kernel level with System execution privileges needed. User interaction is not needed for exploitation.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2025-12-11

Last Modified

2025-12-12

Generated

2026-07-06

AI Q&A

2025-12-11

EPSS Evaluated

2026-07-05

NVD

CVE-2025-36922

Affected Vendors & Products

Vendor	Product	Version / Range
google	android	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-416	The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Attack-Flow Graph

Executive Summary

This vulnerability is a use-after-free issue in the bigo_map function of bigo_iommu.c. It can cause information disclosure and potentially allow a local user to escalate their privileges to the OS kernel level, gaining system execution privileges. Exploiting this vulnerability does not require any user interaction.

Impact Analysis

The vulnerability can lead to local escalation of privilege, allowing an attacker with local access to gain system-level execution privileges. This could compromise the security and integrity of the operating system, potentially allowing unauthorized access to sensitive information or control over the system.

Mitigation Strategies

Apply the latest security patches and updates provided by your device or OS vendor as soon as they become available. Since this vulnerability involves a use-after-free in the OS kernel, updating to the latest kernel or firmware version that includes the fix is critical to mitigate the issue.

Mitigation Strategies

Apply the latest security patches or firmware updates that address this vulnerability as soon as they become available. Since this vulnerability involves a kernel-level issue, updating the operating system or device firmware to the latest security patch level is recommended to mitigate the risk.

Hi! I’m here to help you understand CVE-2025-36922. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70