Device crash via unvalidated TLB address dereference
Published Jan 3, 2022 · Updated Aug 3, 2024
A kernel null-pointer dereference in Qualcomm Snapdragon chipsets allows local users to crash affected devices via a crafted address. The closed-source kernel component dereferences a user-provided address without first validating the corresponding translation lookaside buffer entry. Local access is required; the failure can interrupt service and carries limited confidentiality and integrity impact.
Summary
What happened
A kernel null-pointer dereference in Qualcomm Snapdragon chipsets allows local users to crash affected devices via a crafted address. The closed-source kernel component dereferences a user-provided address without first validating the corresponding translation lookaside buffer entry. Local access is required; the failure can interrupt service and carries limited confidentiality and integrity impact.
The record
- CVE
- CVE-2021-30269
- Published
- Jan 3, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 3, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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