System crash via race-triggered double free
Published Dec 2, 2025 · Updated Dec 2, 2025
Double free in MediaTek AEE Daemon on Android 14.0, 15.0, and 16.0, OpenWRT 21.02 and 23.05, and Yocto 4.0 allows local users to crash the system. A race condition in the aee daemon permits the same resource to be freed twice during concurrent execution; MediaTek has not published the affected function or triggering input. Exploitation requires existing System privilege and no user interaction, and the resulting denial of service is limited to a system crash.
Summary
What happened
Double free in MediaTek AEE Daemon on Android 14.0, 15.0, and 16.0, OpenWRT 21.02 and 23.05, and Yocto 4.0 allows local users to crash the system. A race condition in the aee daemon permits the same resource to be freed twice during concurrent execution; MediaTek has not published the affected function or triggering input. Exploitation requires existing System privilege and no user interaction, and the resulting denial of service is limited to a system crash.
The record
- CVE
- CVE-2025-20765
- Published
- Dec 2, 2025
- Updated
- Dec 2, 2025
- Vendor
- MediaTek
- Product
- MediaTek AEE Daemon
- Classifications
- CWE-362, T1499
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Dec 2, 2025CVE publishedPublication date reported by the CVE source.
- Dec 2, 2025Record 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 14.0, 15.0, 16.0 / openWRT 21.02, 23.05 / Yocto 4.0
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.
Weakness, pattern, technique
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