Unauthenticated code execution via unchecked released buffer
Published Mar 10, 2026 · Updated Mar 10, 2026
Out-of-bounds write in the MFC component of Google Android kernel allows remote attackers to execute code without authentication. __mfc_handle_released_buf in mfc_core_isr.c fails to check bounds while handling a released buffer, permitting a write beyond the intended buffer. No user interaction or prior privileges are required, and successful exploitation provides remote code execution on affected Pixel-family devices.
Summary
What happened
Out-of-bounds write in the MFC component of Google Android kernel allows remote attackers to execute code without authentication. __mfc_handle_released_buf in mfc_core_isr.c fails to check bounds while handling a released buffer, permitting a write beyond the intended buffer. No user interaction or prior privileges are required, and successful exploitation provides remote code execution on affected Pixel-family devices.
The record
- CVE
- CVE-2026-0116
- Published
- Mar 10, 2026
- Updated
- Mar 10, 2026
- Vendor
- Go standard library
- Product
- Android
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 10, 2026CVE publishedPublication date reported by the CVE source.
- Mar 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Android kernel
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo