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
No data.
No data.
No data.
No data.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
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 |
|
Projects
Sign in to view the affected projects.
MITRE
Status: PUBLISHED
Assigner: Google_Devices
Published:
Updated: 2026-11-10T19:22:20.438Z
Reserved: 2026-07-06T06:27:19.075Z
Link: CVE-2026-59609
Vulnrichment
No data.
NVD
Status : Awaiting Analysis
Published: 2026-11-10T20:19:31.283
Modified: 2026-11-10T21:46:40.043
Link: CVE-2026-59609
Redhat
No data.
OpenCVE Enrichment
No data.
Weaknesses
No weakness.