cve.bz

CVE-2026-25266 qualcomm: Out-of-bounds Write

7.8 highEPSS 0.07%

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

On this page
Memory corruption while processing IOCTL command when device is in power-save state.

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.07% (unchanged from 0.07% a week ago; 0.07% 30 days ago) estimated probability of exploitation activity in the next 30 days; 0th 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: partial, assessed 2026-05-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.
CWEs
CWE-787 Out-of-bounds Write
CWE-749 Exposed Dangerous Method or Function
OWASP Top 10
A01:2025 Broken Access Control
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-25266 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-25266?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-25266?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-25266 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-25266

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-25266](https://cve.bz/cve/badge/CVE-2026-25266.svg)](https://cve.bz/cve/CVE-2026-25266)

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Qualcomm, Inc. SnapdragonCologne
Qualcomm, Inc. SnapdragonFastConnect 6900
Qualcomm, Inc. SnapdragonFastConnect 7800
Qualcomm, Inc. SnapdragonSC8380XP
Qualcomm, Inc. SnapdragonSnapdragon AR1 Gen 1 Platform
Qualcomm, Inc. SnapdragonWCD9378C
Qualcomm, Inc. SnapdragonWCD9380
Qualcomm, Inc. SnapdragonWCD9385
Qualcomm, Inc. SnapdragonWCN7861
Qualcomm, Inc. SnapdragonWCN7880
Qualcomm, Inc. SnapdragonWSA8830
Qualcomm, Inc. SnapdragonWSA8832
Qualcomm, Inc. SnapdragonWSA8835
Qualcomm, Inc. SnapdragonWSA8840
Qualcomm, Inc. SnapdragonWSA8845
Qualcomm, Inc. SnapdragonWSA8845H
Qualcomm, Inc. SnapdragonX2000077
Qualcomm, Inc. SnapdragonX2000086
Qualcomm, Inc. SnapdragonX2000090
Qualcomm, Inc. SnapdragonX2000092
Qualcomm, Inc. SnapdragonX2000094
Qualcomm, Inc. SnapdragonXG101002
Qualcomm, Inc. SnapdragonXG101032
Qualcomm, Inc. SnapdragonXG101039

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON