CVE Intelligence
Skip to main content
CISA KEVhighMemory Corruption

CVE-2024-43047

CVE-2024-43047 — Qualcomm Multiple Chipsets Use-After-Free Vulnerability

Memory corruption while maintaining memory maps of HLOS memory.

Published Updated Sources: NVD, CISA, FIRST EPSS

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Oct 8, 2024

EPSS

1%

ahead of 49% of scored CVEs

Affects

qualcomm

64 products listed

CVSS base

7.8

high

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade snapdragon to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

Federal deadline Oct 29, 2024 — passed 685 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

  • Identify exposed assets running affected vendor/product/version combinations.
  • Treat as emergency remediation because CISA KEV status is present.
  • Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

VendorProductVersionsStatus
qualcommsnapdragonVulnerable
qualcommfastconnect_6700_firmwareVulnerable
qualcommfastconnect_6800_firmwareVulnerable
qualcommfastconnect_6900_firmwareVulnerable
qualcommfastconnect_7800_firmwareVulnerable
qualcommqam8295p_firmwareVulnerable
qualcommqca6174a_firmwareVulnerable
qualcommqca6391_firmwareVulnerable
qualcommqca6426_firmwareVulnerable
qualcommqca6436_firmwareVulnerable
qualcommqca6574au_firmwareVulnerable
qualcommqca6584au_firmwareVulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Local

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
7.8CVSS 3.1high1.85.9qualcomm.com (CNA)

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Weakness & attack patterns

  • CWE-416Use After Free

Inferred from the weakness class — not observed against this CVE.

CAPEC-100 · Overflow BuffersCAPEC-123 · Buffer Manipulation

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

Listed

Oct 8, 2024

Federal deadline

Oct 29, 2024

passed 685 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

  1. 2026
  2. Added · CVSS 3.1 7.8 (AV:L)

    Jun 17, 2026 · NVD

  3. 2024
  4. Added to CISA KEV catalog

    Oct 8, 2024 · CISA

  5. Initial · CVE published

    Oct 7, 2024 · NVD

References

4 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1

What should defenders know first?

CVE-2024-43047 is Qualcomm Multiple Chipsets Use-After-Free Vulnerability, a high vulnerability affecting snapdragon, fastconnect_6700_firmware, fastconnect_6800_firmware, fastconnect_6900_firmware, fastconnect_7800_firmware, qam8295p_firmware, qca6174a_firmware, qca6391_firmware, qca6426_firmware, qca6436_firmware, qca6574au_firmware, qca6584au_firmware, qca6595_firmware, qca6595au_firmware, qca6688aq_firmware, qca6696_firmware, qca6698aq_firmware, qcs410_firmware, qcs610_firmware, qcs6490_firmware, qualcomm_video_collaboration_vc1_platform_firmware, qualcomm_video_collaboration_vc3_platform_firmware, sa4150p_firmware, sa4155p_firmware, sa6145p_firmware, sa6150p_firmware, sa6155p_firmware, sa8145p_firmware, sa8150p_firmware, sa8155p_firmware, sa8195p_firmware, sa8295p_firmware, sd660_firmware, sd865_5g_firmware, sg4150p_firmware, snapdragon_660_mobile_platform_firmware, snapdragon_680_4g_mobile_platform_firmware, snapdragon_8_gen_1_mobile_platform_firmware, snapdragon_865_5g_mobile_platform_firmware, snapdragon_888_5g_mobile_platform_firmware, snapdragon_auto_5g_modem_rf_firmware, snapdragon_auto_5g_modem_rf_gen_2_firmware, snapdragon_x55_5g_modem_rf_system_firmware, snapdragon_xr2_5g_platform_firmware, sw5100_firmware, sw5100p_firmware, sxr2130_firmware, wcd9335_firmware, wcd9341_firmware, wcd9370_firmware, wcd9375_firmware, wcd9380_firmware, wcd9385_firmware, wcn3950_firmware, wcn3980_firmware, wcn3988_firmware, wcn3990_firmware, wsa8810_firmware, wsa8815_firmware, wsa8830_firmware, wsa8835_firmware, snapdragon_865_5g_firmware, snapdragon_870_5g_mobile_platform_firmware, sm6225_ad_firmware from qualcomm. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2024-43047. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.8 describes technical severity, while EPSS 1% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.