cve.bz

CVE-2026-21366 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 processing a packet with a size close to the maximum allowed value.

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-15. 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 2026-08-04. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-21366 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-21366?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-21366?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-2026-21366 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.

Badge for a README or a site

CVE-2026-21366

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-21366](https://cve.bz/cve/badge/CVE-2026-21366.svg)](https://cve.bz/cve/CVE-2026-21366)

HTML:

<a href="https://cve.bz/cve/CVE-2026-21366"><img src="https://cve.bz/cve/badge/CVE-2026-21366.svg" alt="CVE-2026-21366"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Qualcomm, Inc. SnapdragonLeMans_AU_LGIT
Qualcomm, Inc. SnapdragonLeMansAU
Qualcomm, Inc. SnapdragonQAM8255P
Qualcomm, Inc. SnapdragonQAM8295P
Qualcomm, Inc. SnapdragonQAM8620P
Qualcomm, Inc. SnapdragonQAMSRV1H
Qualcomm, Inc. SnapdragonQAMSRV1M
Qualcomm, Inc. SnapdragonQCA6574AU
Qualcomm, Inc. SnapdragonQCA6595
Qualcomm, Inc. SnapdragonQCA6595AU
Qualcomm, Inc. SnapdragonQCA6688AQ
Qualcomm, Inc. SnapdragonQCA6696
Qualcomm, Inc. SnapdragonQCA6698AQ
Qualcomm, Inc. SnapdragonQCA6797AQ
Qualcomm, Inc. SnapdragonQCA8695AU
Qualcomm, Inc. SnapdragonSA6145P
Qualcomm, Inc. SnapdragonSA6150P
Qualcomm, Inc. SnapdragonSA6155P
Qualcomm, Inc. SnapdragonSA7255P
Qualcomm, Inc. SnapdragonSA7775P
Qualcomm, Inc. SnapdragonSA8145P
Qualcomm, Inc. SnapdragonSA8150P
Qualcomm, Inc. SnapdragonSA8155P
Qualcomm, Inc. SnapdragonSA8195P
Qualcomm, Inc. SnapdragonSA8255P
Qualcomm, Inc. SnapdragonSA8295P
Qualcomm, Inc. SnapdragonSA8540P
Qualcomm, Inc. SnapdragonSA8620P
Qualcomm, Inc. SnapdragonSA8770P
Qualcomm, Inc. SnapdragonSA9000P
Qualcomm, Inc. SnapdragonSRV1H
Qualcomm, Inc. SnapdragonSRV1L
Qualcomm, Inc. SnapdragonSRV1M

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