MediaTek MT7922 Firmware vulnerabilities

6 CVEs affecting MediaTek MT7922 Firmware, 0 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2026-20495, published 2026-08-03.

Highest priority

Known exploited (CISA KEV) first, then by EPSS exploit probability.

CVE-2025-20672, published 2025-06-02. Critical severity, CVSS 9.8. EPSS: 0.6% chance of exploitation in the next 30 days. In Bluetooth driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with User execution privileges needed. User interaction…
CVE-2026-20482, published 2026-08-03. Medium severity, CVSS 6.5. EPSS: 0.3% chance of exploitation in the next 30 days. In wlan STA FW, there is a possible system becoming unresponsive due to logging. This could lead to remote (proximal/adjacent) denial of service with no additional execution privileges needed. User…
CVE-2025-20673, published 2025-06-02. Medium severity, CVSS 5.5. EPSS: 0.2% chance of exploitation in the next 30 days. In wlan STA driver, there is a possible system crash due to an uncaught exception. This could lead to local denial of service with User execution privileges needed. User interaction is not needed for…
CVE-2025-20675, published 2025-06-02. Medium severity, CVSS 5.5. EPSS: 0.2% chance of exploitation in the next 30 days. In wlan STA driver, there is a possible system crash due to an uncaught exception. This could lead to local denial of service with User execution privileges needed. User interaction is not needed for…
CVE-2026-20495, published 2026-08-03. High severity, CVSS 7.8. EPSS: 0.2% chance of exploitation in the next 30 days. In Bluetooth driver, there is a possible permission bypass due to a missing permission check. This could lead to local escalation of privilege with User execution privileges needed. User interaction…
CVE-2026-20456, published 2026-06-01. Medium severity, CVSS 5.5. EPSS: 0.1% chance of exploitation in the next 30 days. In wlan STA driver, there is a possible system crash due to a missing bounds check. This could lead to local denial of service with User execution privileges needed. User interaction is not needed…