Qualcomm Multiple Chipsets Use-After-Free Vulnerability
Qualcomm, Inc. — Snapdragon
Memory corruption while maintaining memory maps of HLOS memory.
7.8
0.7%
Vector breakdown
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- Oct 7, 2024
- Modified
- Oct 21, 2025
- Added to KEV
- Oct 8, 2024
- Federal patch due
- Oct 29, 2024
CISA required action
Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.
Weakness classification
Proof-of-concept & exploitation references
Weaponization
Public repositories whose name or description references CVE-2024-43047, found via a live GitHub search at request time. These are community-sourced signals, not a verified working exploit — cross-check each one before relying on it, and treat higher star counts and recent activity as (weak) corroboration, not proof.
No public GitHub repositories referencing CVE-2024-43047 were found at last check. Absence here is not proof no exploit exists — see the references below for vendor advisories and write-ups.
References
Frequently asked questions
What is CVE-2024-43047?
Memory corruption while maintaining memory maps of HLOS memory.
How severe is CVE-2024-43047?
CVE-2024-43047 has a CVSS base score of 7.8 out of 10 (CVSS 3.1).
Is CVE-2024-43047 actively exploited in the wild?
Yes. CVE-2024-43047 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added Oct 8, 2024, meaning CISA has confirmed evidence of active exploitation.
What is the EPSS score for CVE-2024-43047?
0.7% - meaning FIRST.org's EPSS model estimates a 0.7% probability this vulnerability will be exploited in the wild within 30 days (50% percentile among all scored CVEs).
What type of vulnerability is CVE-2024-43047?
CVE-2024-43047 is classified under CWE-416 (CWE-416 Use After Free).
Cross-checked against
Impactr finds and proves whether CVE-2024-43047 — or flaws like it — are actually reachable in your own web apps and APIs, with a reproducible exploit as evidence.