How severe is CVE-2025-20705?

CVE-2025-20705 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2025-20705 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-20705?

CVE-2025-20705 primarily affects Linuxfoundation Yocto. In total, 7 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2025-20705?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-20705 have an EU (EUVD) identifier?

Yes. CVE-2025-20705 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-26384.

When was CVE-2025-20705 published?

CVE-2025-20705 was published on 2025-09-01 and last updated on 2026-06-17.

CVE-2025-20705

CVE-2025-20705 is a high-severity vulnerability in Linuxfoundation Yocto with a CVSS 3.x base score of 7.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-416.

Key facts

Severity: High (CVSS 3.x base score 7.8)
EPSS exploit prediction: 0% (1st percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-26384
Weakness: CWE-416
Affected product: Linuxfoundation Yocto
Published: 2025-09-01
Last modified: 2026-06-17

Description

In monitor_hang, 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: ALPS09989078; Issue ID: MSV-3964.

Frequently asked questions

What is CVE-2025-20705?: In monitor_hang, 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: ALPS09989078; Issue ID: MSV-3964.
How severe is CVE-2025-20705?: CVE-2025-20705 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-20705 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-20705?: CVE-2025-20705 primarily affects Linuxfoundation Yocto. In total, 7 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2025-20705?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-20705 have an EU (EUVD) identifier?: Yes. CVE-2025-20705 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-26384.
When was CVE-2025-20705 published?: CVE-2025-20705 was published on 2025-09-01 and last updated on 2026-06-17.

References

https://corp.mediatek.com/product-security-bulletin/September-2025

Affected products (7)

cpe:2.3:a:linuxfoundation:yocto:2.6:*:*:*:*:*:*:*
cpe:2.3:o:google:android:13.0:*:*:*:*:*:*:*
cpe:2.3:o:google:android:14.0:*:*:*:*:*:*:*
cpe:2.3:o:google:android:15.0:*:*:*:*:*:*:*
cpe:2.3:o:google:android:16.0:*:*:*:*:*:*:*
cpe:2.3:o:openwrt:openwrt:19.07.0:-:*:*:*:*:*:*
cpe:2.3:o:openwrt:openwrt:21.02.0:-:*:*:*:*:*:*

More vulnerabilities in Linuxfoundation Yocto

CVE-2024-20148 — Critical (CVSS 9.8): In wlan STA FW, there is a possible out of bounds write due to improper input validation. This could lead to remote…
CVE-2024-20080 — Critical (CVSS 9.8): In gnss service, there is a possible escalation of privilege due to improper certificate validation. This could lead to…
CVE-2024-20040 — High (CVSS 8.8): In wlan firmware, there is a possible out of bounds write due to improper input validation. This could lead to remote…
CVE-2024-25626 — High (CVSS 8.8): Yocto Project is an open source collaboration project that helps developers create custom Linux-based systems…
CVE-2024-20104 — High (CVSS 8.4): In da, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of…
CVE-2024-20053 — High (CVSS 8.4): In flashc, there is a possible out of bounds write due to an uncaught exception. This could lead to local escalation of…

All CVEs affecting Linuxfoundation Yocto →

Other CWE-416 (Use After Free) vulnerabilities

CVE-2026-13782 — Critical (CVSS 10.0): Use after free in Browser in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the…
CVE-2026-4725 — Critical (CVSS 10.0): Sandbox escape due to use-after-free in the Graphics: Canvas2D component. This vulnerability was fixed in Firefox 149…
CVE-2026-4688 — Critical (CVSS 10.0): Sandbox escape due to use-after-free in the Disability Access APIs component. This vulnerability was fixed in Firefox…
CVE-2025-24085 — Critical (CVSS 10.0): A use after free issue was addressed with improved memory management. This issue is fixed in iOS 18.3 and iPadOS 18.3,…
CVE-2024-43102 — Critical (CVSS 10.0): Concurrent removals of certain anonymous shared memory mappings by using the UMTX_SHM_DESTROY sub-request of…
CVE-2021-32495 — Critical (CVSS 10.0): Radare2 has a use-after-free vulnerability in pyc parser's get_none_object function. Attacker can read freed memory…

Browse all CWE-416 (Use After Free) vulnerabilities →