# CVE-2025-59605: Qualcomm Snapdragon memory corruption in device identifier processing

Source: https://junglewise.ai/threats/cve-2025-59605-qualcomm-snapdragon-memory-corruption-in-device-identifier  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-01. Updated: 2026-06-01  
License: CC BY 4.0 with a link back

CVE-2025-59605 · Severity: high · CVSS 7.8 · Published 2026-06-01

A security vulnerability exists in Qualcomm chipsets used in many mobile devices. The flaw occurs when the system processes device identification information that is longer than expected, leading to memory corruption. If exploited, a malicious application already on the device could gain deeper access, potentially compromising user data or taking control of core system functions.

Technologies: [Qualcomm Snapdragon Mobile](https://junglewise.ai/threats/technologies/snapdragon-mobile). Vendors: [Qualcomm](https://junglewise.ai/threats/vendors/qualcomm).

## Quick answers

**Is CVE-2025-59605 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-59605 being exploited in the wild.

**How severe is CVE-2025-59605?** High severity, with a CVSS score of 7.8, published 1 June 2026.

**Which products and versions are affected?** Qualcomm Snapdragon Mobile.

**Is there a fix for CVE-2025-59605?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2025-59605 attacked?** It is attacked with local access, in device firmware.

**Am I affected by CVE-2025-59605?** Check whether you run Qualcomm Snapdragon Mobile. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A memory corruption vulnerability, specifically an out-of-bounds write (CWE-787), exists in Qualcomm firmware/software during the processing of device identifier strings. The issue is triggered when a string exceeds the statically defined buffer length, allowing an attacker to overwrite adjacent memory. This is a local attack requiring low privileges, typically achieved through a malicious application running on the host OS. Successful exploitation can lead to a complete loss of confidentiality, integrity, and availability at the firmware or kernel level. Qualcomm has addressed this in their June 2026 security bulletin.

## Affected products

- Qualcomm Snapdragon Mobile

## Timeline

- 2026-06-01: advisory: Qualcomm published the security bulletin and NVD entry.

## References

- [https://docs.qualcomm.com/product/publicresources/securitybulletin/june-2026-bulletin.html](https://docs.qualcomm.com/product/publicresources/securitybulletin/june-2026-bulletin.html)

## Related threats

- [Qualcomm Snapdragon memory corruption in HT40 channel switching](https://junglewise.ai/threats/cve-2026-25268-qualcomm-snapdragon-memory-corruption-in-ht40-channel-switching)
- [Qualcomm Snapdragon memory corruption via TOCTOU in shared buffers](https://junglewise.ai/threats/cve-2026-25260-qualcomm-snapdragon-memory-corruption-via-toctou-in-shared)
- [Qualcomm Chipset memory corruption in IOCTL escape operations](https://junglewise.ai/threats/cve-2026-25259-qualcomm-chipset-memory-corruption-in-ioctl-escape-operations)
- [Qualcomm Snapdragon memory corruption in IOCTL escape operations](https://junglewise.ai/threats/cve-2026-25258-qualcomm-snapdragon-memory-corruption-in-ioctl-escape-operations)
- [Qualcomm Snapdragon memory corruption in fastboot display mode command](https://junglewise.ai/threats/cve-2026-24092-qualcomm-snapdragon-memory-corruption-in-fastboot-display-mode)