Memory corruption via unchecked freed DRM structure
Published Jun 14, 2022 · Updated Aug 3, 2024
A use-after-free in Qualcomm Snapdragon Display DRM code allows local users to corrupt memory through DRM file handling. After freeing a DRM file structure, the Display code accesses its status without a null check, leaving a dangling reference available for reuse. Local access is required; Qualcomm reports confidentiality, integrity, and availability impact but does not disclose the reachable code path or concrete post-corruption outcome.
Summary
What happened
A use-after-free in Qualcomm Snapdragon Display DRM code allows local users to corrupt memory through DRM file handling. After freeing a DRM file structure, the Display code accesses its status without a null check, leaving a dangling reference available for reuse. Local access is required; Qualcomm reports confidentiality, integrity, and availability impact but does not disclose the reachable code path or concrete post-corruption outcome.
The record
- CVE
- CVE-2021-30334
- Published
- Jun 14, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 14, 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.
Weakness, pattern, technique
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