4.2

CVE-2025-20745

In apusys, there is a possible memory corruption due to use after free. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: ALPS10095441; Issue ID: MSV-4294.
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
Google ≫ Android Version 13.0
   Mediatek ≫ Mt2718 Version -
   Mediatek ≫ Mt6989 Version -
   Mediatek ≫ Mt6991 Version -
   Mediatek ≫ Mt8370 Version -
   Mediatek ≫ Mt8390 Version -
   Mediatek ≫ Mt8395 Version -
   Mediatek ≫ Mt8676 Version -
   Mediatek ≫ Mt8678 Version -
   Mediatek ≫ Mt87920 Version -
Google ≫ Android Version 14.0
   Mediatek ≫ Mt2718 Version -
   Mediatek ≫ Mt6989 Version -
   Mediatek ≫ Mt6991 Version -
   Mediatek ≫ Mt8370 Version -
   Mediatek ≫ Mt8390 Version -
   Mediatek ≫ Mt8395 Version -
   Mediatek ≫ Mt8676 Version -
   Mediatek ≫ Mt8678 Version -
   Mediatek ≫ Mt87920 Version -
Google ≫ Android Version 15.0
   Mediatek ≫ Mt2718 Version -
   Mediatek ≫ Mt6989 Version -
   Mediatek ≫ Mt6991 Version -
   Mediatek ≫ Mt8370 Version -
   Mediatek ≫ Mt8390 Version -
   Mediatek ≫ Mt8395 Version -
   Mediatek ≫ Mt8676 Version -
   Mediatek ≫ Mt8678 Version -
   Mediatek ≫ Mt87920 Version -
VulnDex Vulnerability Enrichment
Diese Information steht angemeldeten Benutzern zur Verfügung. Login Login
Zu dieser CVE wurde keine Warnung gefunden.
EPSS Metriken
Typ Quelle Score Percentile
EPSS FIRST.org 0.08% 0.001
CVSS Metriken
Quelle Base Score Exploit Score Impact Score Vector String
NIST 4.2 0.8 3.4
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L
CISA-ADP 4.2 0.8 3.4
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L
CWE-416 Use After Free

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

https://corp.mediatek.com/product-security-bulletin/November-2025
Vendor Advisory