Local system crash via WLAN null-pointer dereference
Published Jun 2, 2025 · Updated Jun 3, 2025
Null pointer dereference in MediaTek WLAN STA drivers in NB SDK 3.6 and earlier allows local users to crash affected systems. The driver leaves an exception uncaught when it encounters the null-pointer condition, terminating the system instead of handling the fault. User-level code can trigger the crash without user interaction, but published details do not identify the specific input or driver function.
Summary
What happened
Null pointer dereference in MediaTek WLAN STA drivers in NB SDK 3.6 and earlier allows local users to crash affected systems. The driver leaves an exception uncaught when it encounters the null-pointer condition, terminating the system instead of handling the fault. User-level code can trigger the crash without user interaction, but published details do not identify the specific input or driver function.
The record
- CVE
- CVE-2025-20676
- Published
- Jun 2, 2025
- Updated
- Jun 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 2, 2025CVE publishedPublication date reported by the CVE source.
- Jun 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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