PatchSiren cyber security CVE debrief
CVE-2025-20799 MediaTek, Inc. CVE debrief
A high-severity CVE-2025-20799 vulnerability exists in c2ps, potentially leading to local escalation of privilege. The issue arises from a use-after-free error and requires System privileges for exploitation. User interaction is not necessary. Affected versions and patches are detailed in vendor advisories. This vulnerability has a CVSS score of 7.8 and is classified as HIGH severity. System administrators should assess exposure and apply patches from Mediatek's January 2026 security bulletin.
- Vendor
- MediaTek, Inc.
- Product
- MediaTek chipset
- CVSS
- HIGH 7.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-01-06
- Original CVE updated
- 2026-09-30
- Advisory published
- 2026-01-06
- Advisory updated
- 2026-09-30
Who should care
System administrators and security teams responsible for Mediatek-based systems and Android devices should assess exposure and apply patches from Mediatek's January 2026 security bulletin. They should also verify and update affected Android versions, monitor system logs for suspicious activity, and review compensating controls for exposed systems.
Why it matters
CVE-2025-20799 is a high-severity vulnerability in c2ps that allows local escalation of privilege. It requires System privileges for exploitation and no user interaction. Affected systems should prioritize patching and verification.
- Local privilege escalation possible
- System privilege required for exploitation
- No user interaction needed for exploitation
- Patching and verification recommended
Technical summary
The CVE-2025-20799 vulnerability is caused by a use-after-free error in c2ps, potentially allowing local escalation of privilege. The vulnerability has a CVSS score of 7.8 and is classified as HIGH severity. Exploitation requires System privileges but not user interaction. Affected systems should prioritize patching and verification. No user interaction is needed for exploitation. This vulnerability affects Mediatek-based systems and Android devices running affected versions. System administrators and security teams should assess exposure.
Defensive priority
High-priority patching and verification recommended for affected systems
Recommended defensive actions
- Apply patches from Mediatek's January 2026 security bulletin
- Verify and update affected Android versions
- Monitor system logs for suspicious activity
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and NVD entry provide details on the vulnerability. Vendor advisory from Mediatek offers patch information. The vulnerability has a CVSS score of 7.8 and is classified as HIGH severity. No additional information is available on exploitation or affected versions beyond vendor advisories and CVE details. Defenders should verify affected Mediatek-based systems and Android devices.
Sources and references
Verified primary and authoritative sources
-
CVE-2025-20799 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2025-20799
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2025-20799 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2025-20799
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://corp.mediatek.com/product-security-bulletin/January-2026
[email protected] - Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.