In fence_manager_extract_iif of fence_manager.c, there is a possible way to corrupt kernel memory via fence identifier reuse due to a use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Metrics
Affected Vendors & Products
References
History
Fri, 13 Nov 2026 22:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Kernel Memory Corruption via Fence Identifier Reuse Leading to Local Privilege Escalation |
Fri, 13 Nov 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-416 | |
| Metrics |
cvssV3_1
|
Fri, 13 Nov 2026 13:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Google
Google android |
|
| Vendors & Products |
Google
Google android |
Thu, 12 Nov 2026 20:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Kernel Memory Corruption via Fence Identifier Reuse Leading to Local Privilege Escalation | |
| Weaknesses | CWE-416 |
Thu, 12 Nov 2026 03:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Kernel Memory Corruption via Fence Identifier Reuse Leading to Local Privilege Escalation | |
| Weaknesses | CWE-416 |
Tue, 10 Nov 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In fence_manager_extract_iif of fence_manager.c, there is a possible way to corrupt kernel memory via fence identifier reuse due to a use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. | |
| References |
|
Status: PUBLISHED
Assigner: Google_Devices
Published: 2026-11-10T19:22:20.438Z
Updated: 2026-11-13T14:02:08.579Z
Reserved: 2026-07-06T06:27:19.075Z
Link: CVE-2026-59609
No data.
Status : Awaiting Analysis
Published: 2026-11-10T20:19:31.283
Modified: 2026-11-13T14:17:59.130
Link: CVE-2026-59609
No data.