CVE-2026-24075: Qualcomm device control handler memory corruption via concurrent IOCTL requests
CVE-2026-24075 · Severity: high · CVSS 7.8 · Published 2026-09-17
A Qualcomm device control handler contains a memory corruption vulnerability triggered when multiple threads simultaneously issue IOCTL requests due to improper synchronization. An attacker with local access to the device could exploit this race condition to corrupt kernel memory, potentially leading to denial of service or privilege escalation.
No. Junglewise Threat Intelligence has no report of CVE-2026-24075 being exploited in the wild.
How severe is CVE-2026-24075?
High severity, with a CVSS score of 7.8, published 17 September 2026.
Which products and versions are affected?
Qualcomm <UNKNOWN> <UNKNOWN>.
Is there a fix for CVE-2026-24075?
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-2026-24075 attacked?
It is attacked with local access.
Am I affected by CVE-2026-24075?
Check whether you run Qualcomm Aqt1000, Qualcomm AQT1000 Firmware, Qualcomm Cologne or one of the others listed. 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
The vulnerability is a race condition (CWE-362) in the device control handler's IOCTL request processing logic. The root cause is improper synchronization when multiple threads concurrently issue IOCTL requests, leading to memory corruption. The attack requires local access to trigger concurrent IOCTL calls against the device control interface. Successful exploitation could result in kernel memory corruption, enabling denial of service or potential privilege escalation. A patch is expected from Qualcomm as indicated by the September 2026 security bulletin.