Memory failure via unchecked SKB padding
Published Apr 16, 2020 · Updated Aug 5, 2024
Improper exception handling in Snapdragon Auto and Snapdragon Mobile allows local users to trigger memory failure via crafted SKB padding requests. The SKB path does not correctly handle failure when requested padding cannot be added under low-memory or heavily fragmented conditions. Reaching the condition requires local access to the affected Qualcomm platform; the record does not specify a distinct confidentiality, integrity, or availability outcome beyond memory failure.
Summary
What happened
Improper exception handling in Snapdragon Auto and Snapdragon Mobile allows local users to trigger memory failure via crafted SKB padding requests. The SKB path does not correctly handle failure when requested padding cannot be added under low-memory or heavily fragmented conditions. Reaching the condition requires local access to the affected Qualcomm platform; the record does not specify a distinct confidentiality, integrity, or availability outcome beyond memory failure.
The record
- CVE
- CVE-2019-14122
- Published
- Apr 16, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-755, T1203
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 16, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.
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