cve.bz

CVE-2024-21470 qualcomm: Year 2038 problem, Y2K38, Y2038, Epochalypse

7.8 highEPSS 0.1%

High (7.8) in qualcomm. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
Memory corruption while allocating memory for graphics.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2024-04-01. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
CWE-680 Integer Overflow to Buffer Overflow
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-21470 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-21470?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-21470?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-21470 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Qualcomm, Inc. SnapdragonAQT1000
Qualcomm, Inc. SnapdragonFastConnect 6200
Qualcomm, Inc. SnapdragonFastConnect 6700
Qualcomm, Inc. SnapdragonFastConnect 6800
Qualcomm, Inc. SnapdragonFastConnect 6900
Qualcomm, Inc. SnapdragonFastConnect 7800
Qualcomm, Inc. SnapdragonQCA6391
Qualcomm, Inc. SnapdragonQCA6420
Qualcomm, Inc. SnapdragonQCA6430
Qualcomm, Inc. SnapdragonSC8180X+SDX55
Qualcomm, Inc. SnapdragonSC8380XP
Qualcomm, Inc. SnapdragonSM6250
Qualcomm, Inc. SnapdragonSnapdragon 7c Compute Platform (SC7180-AC)
Qualcomm, Inc. SnapdragonSnapdragon 7c Gen 2 Compute Platform (SC7180-AD) "Rennell Pro"
Qualcomm, Inc. SnapdragonSnapdragon 7c+ Gen 3 Compute
Qualcomm, Inc. SnapdragonSnapdragon 8c Compute Platform (SC8180X-AD) "Poipu Lite"
Qualcomm, Inc. SnapdragonSnapdragon 8c Compute Platform (SC8180XP-AD) "Poipu Lite"
Qualcomm, Inc. SnapdragonSnapdragon 8cx Compute Platform (SC8180X-AA, AB)
Qualcomm, Inc. SnapdragonSnapdragon 8cx Compute Platform (SC8180XP-AC, AF) "Poipu Pro"
Qualcomm, Inc. SnapdragonSnapdragon 8cx Gen 2 5G Compute Platform (SC8180X-AC, AF) "Poipu
Qualcomm, Inc. SnapdragonSnapdragon 8cx Gen 2 5G Compute Platform (SC8180XP-AA, AB)
Qualcomm, Inc. SnapdragonSnapdragon 8cx Gen 3 Compute Platform (SC8280XP-AB, BB)
Qualcomm, Inc. SnapdragonWCD9340
Qualcomm, Inc. SnapdragonWCD9341
Qualcomm, Inc. SnapdragonWCD9380
Qualcomm, Inc. SnapdragonWCD9385
Qualcomm, Inc. SnapdragonWSA8810
Qualcomm, Inc. SnapdragonWSA8815
Qualcomm, Inc. SnapdragonWSA8830
Qualcomm, Inc. SnapdragonWSA8835
Qualcomm, Inc. SnapdragonWSA8840
Qualcomm, Inc. SnapdragonWSA8845
Qualcomm, Inc. SnapdragonWSA8845H

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-680 (11).

References

Check your stackJSON