Local WLAN service interruption via unchecked parameters
Published Feb 6, 2023 · Updated Mar 26, 2025
Out-of-bounds write in the UNISOC WLAN driver on Android 10 through Android 12 allows local users to interrupt WLAN services. The driver fails to validate parameters before performing a memory write, allowing data to be written outside the intended bounds; the affected function and parameters are undisclosed. Exploitation requires high local privileges, and the documented operational consequence is interruption of WLAN services.
Summary
What happened
Out-of-bounds write in the UNISOC WLAN driver on Android 10 through Android 12 allows local users to interrupt WLAN services. The driver fails to validate parameters before performing a memory write, allowing data to be written outside the intended bounds; the affected function and parameters are undisclosed. Exploitation requires high local privileges, and the documented operational consequence is interruption of WLAN services.
The record
- CVE
- CVE-2022-47369
- Published
- Feb 6, 2023
- Updated
- Mar 26, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 6, 2023CVE publishedPublication date reported by the CVE source.
- Mar 26, 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.
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