Memory corruption via frontend allocation race
Published Mar 3, 2025 · Updated Feb 26, 2026
Memory corruption in Qualcomm Snapdragon Auto chipsets allows local users to compromise memory via a frontend allocation message. Qualcomm identifies a TOCTOU race during allocation while processing a frontend message, but does not disclose the affected code path or the checked resource that can change before use. Low-privileged local access is required; successful exploitation can compromise confidentiality, integrity, and availability within the affected security scope.
Summary
What happened
Memory corruption in Qualcomm Snapdragon Auto chipsets allows local users to compromise memory via a frontend allocation message. Qualcomm identifies a TOCTOU race during allocation while processing a frontend message, but does not disclose the affected code path or the checked resource that can change before use. Low-privileged local access is required; successful exploitation can compromise confidentiality, integrity, and availability within the affected security scope.
The record
- CVE
- CVE-2024-53028
- Published
- Mar 3, 2025
- Updated
- Feb 26, 2026
- Vendor
- Qualcomm
- Product
- Snapdragon
- Classifications
- CWE-367
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 3, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=QAM8255P
- Affected versionversion=QAM8295P
- Affected versionversion=QAM8620P
- Affected versionversion=QAM8650P
- Affected versionversion=QAM8775P
- Affected versionversion=QAMSRV1H
- Affected versionversion=QAMSRV1M
- Affected versionversion=QCA6574A
- Affected versionversion=QCA6574AU
- Affected versionversion=QCA6595
- Affected versionversion=QCA6595AU
- Affected versionversion=QCA6688AQ
- Affected versionversion=QCA6696
- Affected versionversion=QCA6698AQ
- Affected versionversion=SA6145P
- Affected versionversion=SA6150P
- Affected versionversion=SA6155
- Affected versionversion=SA6155P
- Affected versionversion=SA7255P
- Affected versionversion=SA7775P
- Affected versionversion=SA8145P
- Affected versionversion=SA8150P
- Affected versionversion=SA8155
- Affected versionversion=SA8155P
- Affected versionversion=SA8195P
- Affected versionversion=SA8255P
- Affected versionversion=SA8295P
- Affected versionversion=SA8540P
- Affected versionversion=SA8620P
- Affected versionversion=SA8650P
- Affected versionversion=SA8770P
- Affected versionversion=SA8775P
- Affected versionversion=SA9000P
- Affected versionversion=SRV1H
- Affected versionversion=SRV1L
- Affected versionversion=SRV1M
What conditions does exploitation require?
What is affected?
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