Android MFC Driver OOB Write Leads to Local Priv Escalation
CVE-2026-0117 Published on March 10, 2026

In mfc_dec_dqbuf of mfc_dec_v4l2.c, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Vendor Advisory NVD

Vulnerability Analysis

CVE-2026-0117 can be exploited with local system access, and does not require authorization privileges or user interaction. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to be very high.

Attack Vector:
LOCAL
Attack Complexity:
LOW
Privileges Required:
NONE
User Interaction:
NONE
Scope:
UNCHANGED
Confidentiality Impact:
HIGH
Integrity Impact:
HIGH
Availability Impact:
HIGH

Weakness Type

What is a Memory Corruption Vulnerability?

The software writes data past the end, or before the beginning, of the intended buffer. Typically, this can result in corruption of data, a crash, or code execution. The software may modify an index or perform pointer arithmetic that references a memory location that is outside of the boundaries of the buffer. A subsequent write operation then produces undefined or unexpected results.

CVE-2026-0117 has been classified to as a Memory Corruption vulnerability or weakness.


Products Associated with CVE-2026-0117

Want to know whenever a new CVE is published for Google Android? stack.watch will email you.

 

Affected Versions

Google Android Version Android kernel is affected by CVE-2026-0117