# CVE-2025-59610: Qualcomm Chipset memory corruption in IOCTL processing

Source: https://junglewise.ai/threats/cve-2025-59610-qualcomm-chipset-memory-corruption-in-ioctl-processing  
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-59610 · Severity: medium · CVSS 6.4 · Published 2026-06-01

A memory corruption vulnerability exists in Qualcomm chipset software when handling specific input/output control requests. An attacker with high-level system privileges could exploit this flaw to cause a system crash or potentially gain unauthorized access to sensitive data. This issue primarily impacts mobile devices and hardware utilizing affected Qualcomm components.

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

## Quick answers

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

**How severe is CVE-2025-59610?** Medium severity, with a CVSS score of 6.4, published 1 June 2026.

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

**Is there a fix for CVE-2025-59610?** 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-59610 attacked?** It is attacked with local access, in device firmware.

**Am I affected by CVE-2025-59610?** 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 Time-of-Check Time-of-Use (TOCTOU) race condition (CWE-367) exists in Qualcomm chipset firmware during the processing of IOCTL requests. The vulnerability is triggered when there is a mismatch in API versions and a concurrent modification of the user-space buffer occurs during processing. A local attacker with high privileges can exploit this race condition to cause memory corruption. This can lead to a complete compromise of confidentiality, integrity, and availability (C/I/A) on the affected system. The attack complexity is high due to the precise timing required to modify the buffer between the check and use phases.

## Affected products

- Qualcomm Snapdragon Mobile

## Timeline

- 2026-06-01: disclosed
- 2026-06-01: advisory

## 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)