cve.bz

CVE-2023-21630 qualcomm: Year 2038 problem, Y2K38, Y2038, Epochalypse

7.8 highEPSS 0.1%Fix available

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

On this page
Memory Corruption in Multimedia Framework due to integer overflow when synx bind is called along with synx signal.

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; 2nd 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-07-11. 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-191 Integer Underflow (Wrap or Wraparound)
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-21630 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-21630?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-21630?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-2023-21630 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. SnapdragonFastConnect 6700
Qualcomm, Inc. SnapdragonFastConnect 6900
Qualcomm, Inc. SnapdragonFastConnect 7800
Qualcomm, Inc. SnapdragonQCA6391
Qualcomm, Inc. SnapdragonQCA6574
Qualcomm, Inc. SnapdragonQCA6574A
Qualcomm, Inc. SnapdragonQCA6574AU
Qualcomm, Inc. SnapdragonQCA6595AU
Qualcomm, Inc. SnapdragonQCA6696
Qualcomm, Inc. SnapdragonSA6155P
Qualcomm, Inc. SnapdragonSA8155P
Qualcomm, Inc. SnapdragonSA8195P
Qualcomm, Inc. SnapdragonSD 8 Gen1 5G
Qualcomm, Inc. SnapdragonSD778G
Qualcomm, Inc. SnapdragonSD888
Qualcomm, Inc. SnapdragonSG4150P
Qualcomm, Inc. SnapdragonSM7315
Qualcomm, Inc. SnapdragonSM7325P
Qualcomm, Inc. SnapdragonSnapdragon 680 4G Mobile Platform
Qualcomm, Inc. SnapdragonSnapdragon 685 4G Mobile Platform (SM6225-AD)
Qualcomm, Inc. SnapdragonSnapdragon 778G 5G Mobile Platform
Qualcomm, Inc. SnapdragonSnapdragon 778G+ 5G Mobile Platform (SM7325-AE)
Qualcomm, Inc. SnapdragonSnapdragon 780G 5G Mobile Platform
Qualcomm, Inc. SnapdragonSnapdragon 782G Mobile Platform (SM7325-AF)
Qualcomm, Inc. SnapdragonSnapdragon 8 Gen 1 Mobile Platform
Qualcomm, Inc. SnapdragonSnapdragon 888 5G Mobile Platform
Qualcomm, Inc. SnapdragonSnapdragon 888+ 5G Mobile Platform (SM8350-AC)
Qualcomm, Inc. SnapdragonSW5100
Qualcomm, Inc. SnapdragonSW5100P
Qualcomm, Inc. SnapdragonWCD9370
Qualcomm, Inc. SnapdragonWCD9375
Qualcomm, Inc. SnapdragonWCD9380
Qualcomm, Inc. SnapdragonWCD9385
Qualcomm, Inc. SnapdragonWCN3950
Qualcomm, Inc. SnapdragonWCN3980
Qualcomm, Inc. SnapdragonWCN3988
Qualcomm, Inc. SnapdragonWCN6740
Qualcomm, Inc. SnapdragonWSA8810
Qualcomm, Inc. SnapdragonWSA8830
Qualcomm, Inc. SnapdragonWSA8835

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.

References

Check your stackJSON