CVE-2026-24075 — Aqt1000 Firmware
HIGHCVE-2026-24075 is a high-severity (CVSS 7.8) CWE-126 vulnerability in qualcomm aqt1000 firmware. No vendor fix is recorded yet; mitigation options are listed below.
Memory Corruption when multiple threads issue concurrent IOCTL requests to the device control handler due to improper synchronization and race conditions.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-24075.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-24075 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Description
Memory Corruption when multiple threads issue concurrent IOCTL requests to the device control handler due to improper synchronization and race conditions.
Affected Products
aqt1000 firmwarequalcommcologne firmwarequalcommfastconnect 6200 firmwarequalcommfastconnect 6700 firmwarequalcommfastconnect 6800 firmwarequalcommfastconnect 6900 firmwarequalcommDetection & mitigation playbook
Vendor / applianceDetect
Inventory every qualcomm aqt1000 firmware deployment and check each version against the affected-products list above.
Remediation status
No patch has shipped for CVE-2026-24075 yet — track the qualcomm aqt1000 firmware advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.
Frequently Asked Questions
Is CVE-2026-24075 being exploited in your environment?
Detect and block the exploit chain at execution, on systems you cannot patch yet.