Kernel failure via unvalidated WDOG registration
Published Feb 11, 2022 · Updated Aug 4, 2024
NULL pointer dereference in Qualcomm Snapdragon WDOG registration allows local users to trigger a kernel failure on affected chipsets. The kernel registration path fails to validate the WDOG structure before dereferencing it, allowing an invalid structure to reach a pointer use. Local access is required; Qualcomm has not disclosed whether exploitation permits effects beyond a kernel failure.
Summary
What happened
NULL pointer dereference in Qualcomm Snapdragon WDOG registration allows local users to trigger a kernel failure on affected chipsets. The kernel registration path fails to validate the WDOG structure before dereferencing it, allowing an invalid structure to reach a pointer use. Local access is required; Qualcomm has not disclosed whether exploitation permits effects beyond a kernel failure.
The record
- CVE
- CVE-2021-35075
- Published
- Feb 11, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 11, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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