CVE-2026-59609 · Infrastructure
NO FIX YET
A use-after-free in the kernel's fence manager (fence_manager.c, fence_manager_extract_iif) lets a local process corrupt kernel memory by reusing a fence identifier. An attacker who can run code on the device can escalate to higher privileges, with no user interaction needed.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
The description names only the kernel's fence manager code as the flaw and says exploitation needs no extra execution privileges and no user interaction. The sources do not name affected product versions or device families, so whether a given device is exposed is unknown.
Not affected if unknown
Who cares android, linux-kernel
Unknown from the sources.
No fix yet, per the sources.
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.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.