CVE-2026-21370: Qualcomm Wireless Chipset Firmware Memory Corruption Vulnerability
Qualcomm Wi-Fi and cellular chipset firmware contains a memory corruption vulnerability that can be triggered when input validation fails to properly check batch size and buffer plane count parameters. An attacker with local access and low privileges can exploit this flaw to read or write memory, potentially affecting system stability or confidentiality. The vulnerability affects dozens of Qualcomm chipsets across FastConnect, G3X, IQ, and QCA product lines.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 5.3 MEDIUM · CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L
- Weaknesses (CWE)
- CWE-787
- Affected products
- 182 configuration(s)
- Published / Modified
- 2026-07-06 / 2026-07-07
NVD description (verbatim)
Memory Corruption when validating input batch size and buffer plane count exceeds maximum allowed values.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-21370 is an out-of-bounds write vulnerability (CWE-787) in Qualcomm wireless chipset firmware. The flaw exists in input validation logic that checks batch size and buffer plane count against maximum allowed values. When these checks fail to enforce limits correctly, an attacker can cause memory corruption. The CVSS 3.1 vector (AV:L/AC:H/PR:L/UI:N/S:C) indicates local attack surface, high complexity (likely requiring specific conditions to trigger), low privilege requirement, and cross-boundary impact. The vulnerability affects confidentiality, integrity, and availability of the affected system.
Business impact
Organizations deploying Qualcomm wireless chipsets in enterprise or critical infrastructure may face increased risk of system crashes, data leakage, or unauthorized firmware-level manipulation. The local-attack requirement limits exposure in remote deployment scenarios, but insider threats or co-tenant attacks in multi-tenant environments could exploit this vector. Affected devices include WiFi 6 and cellular modems widely used in laptops, access points, and network equipment. Unpatched firmware could be leveraged for lateral movement or privilege escalation in compromised systems.
Affected systems
The vulnerability impacts a broad ecosystem of Qualcomm wireless chipsets: FastConnect series (6700, 6900, 7800), G3X Gen 2, IQ-9075, LeMans (AU LGIT and standard variants), NetRani, Pandeiro, QAM8255P, QAMSRV1H/M, QCA6595/AU, QCA6678AQ, QCA6698AQ/AU, QCA6797AQ, and QCM4490/8838. Both the chipset hardware and associated firmware versions are listed as vulnerable. Manufacturers integrating these components into laptops, routers, wireless access points, industrial IoT devices, and cellular modems should prioritize inventory and patch assessment.
Exploitability
Exploitation requires local system access and low user privileges—a significant constraint that reduces real-world risk for remote attack scenarios. However, the high complexity rating suggests special conditions or precise input sequences are necessary to reliably trigger memory corruption. An attacker must craft specific batch size or buffer plane parameters that bypass validation. This is not a trivial remote worm vector, but represents a meaningful risk in insider threat models, guest-to-host escape scenarios, and co-tenant cloud environments. No public exploit code has been indexed in CISA's Known Exploited Vulnerabilities catalog.
Remediation
Apply firmware updates from Qualcomm that correct the input validation logic for batch size and buffer plane count checks. Verify patch availability through the Qualcomm security advisory corresponding to this CVE. Organizations should test patches in non-production environments first, given the firmware-level nature of the fix and potential device compatibility considerations. For products nearing end-of-life, evaluate whether extended support or device replacement is more cost-effective than patching.
Patch guidance
Contact your Qualcomm vendor or device manufacturer to obtain the latest firmware release addressing CVE-2026-21370. Patch availability and version numbers should be verified directly through official security advisories rather than assumed. Firmware updates typically require device reboot and should be scheduled during maintenance windows. Some devices may require out-of-band management (BMC, IPMI, or vendor-specific recovery modes) if the main OS is compromised. Test patches on non-critical hardware first to confirm stability and that no regression occurs in wireless connectivity or performance.
Detection guidance
Monitor system logs for unexpected memory access violations, segmentation faults, or crashes in wireless driver or firmware processes. Network security teams should look for suspicious attempts to load or flash unsigned firmware on managed devices. Endpoint detection and response (EDR) solutions should flag attempts to manipulate memory regions adjacent to wireless driver buffers. Firmware audit tools and supply-chain validation can confirm whether devices are running patched versions. Cross-reference device inventory against the affected product list to identify scope.
Why prioritize this
This vulnerability merits medium-priority remediation in most environments. While the CVSS score of 5.3 reflects the local-access requirement and conditional trigger, the extensive list of affected Qualcomm chipsets means a large installed base is potentially exposed. The combination of low privilege requirement and cross-boundary impact (C:L/I:L/A:L) suggests meaningful post-exploitation capability. Organizations with high concentrations of Qualcomm-based WiFi 6 devices or cellular modems, or those with elevated insider threat risk, should accelerate patching.
Risk score, explained
The CVSS 3.1 score of 5.3 (MEDIUM) reflects the balance between exploitability constraints and impact scope. The local attack vector and high complexity significantly reduce the attack surface compared to remote vulnerabilities. However, the low privilege requirement and ability to affect system stability, data confidentiality, and integrity across security boundaries elevate the rating above LOW. Organizations should apply risk context: device role, network segmentation, user privilege levels, and whether the affected chipset is internet-facing or isolated internally.
Frequently asked questions
Does this vulnerability require network access to exploit?
No. CVE-2026-21370 requires local system access. An attacker must already have a user account or shell access on the device. This makes it a lateral-movement or post-exploitation risk rather than a direct remote attack vector.
What is the practical attack scenario?
A low-privilege local user or container could craft specific batch size and buffer plane parameters to trigger memory corruption in the wireless firmware, potentially leaking kernel memory, escalating privileges, or causing denial of service. Multi-tenant cloud environments and systems with untrusted guest users face higher risk.
Are there workarounds if I cannot patch immediately?
Mitigate by restricting local user access via privilege separation, disabling unnecessary wireless features if feasible, or isolating affected devices from untrusted networks. However, these are temporary measures. Firmware patching is the proper fix. Contact Qualcomm or your device vendor for patch ETA if unavailable.
How do I check if my device is affected?
Cross-reference your device model and chipset against the vendor_products list (FastConnect, G3X, IQ, QCA, QCM series). Obtain the current firmware version from device settings or management console. Consult your vendor's security advisory to confirm whether your firmware version is vulnerable and when a patch will be available.
This analysis is provided for informational purposes and reflects publicly available data as of the publication date. Patch version numbers, availability timelines, and vendor-specific guidance should be verified directly with Qualcomm security advisories and device manufacturers. No exploit code or detailed attack reproduction steps are provided. Organizations are responsible for assessing risk within their own environment and conducting thorough testing before deploying patches in production. Source: NVD (public-domain), retrieved 2026-08-15. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2025-59614MEDIUMQualcomm Memory Corruption in RNG Command Handling
- CVE-2026-21368MEDIUMQualcomm JPEG Parser Memory Corruption in Snapdragon and FastConnect
- CVE-2026-21369MEDIUMQualcomm Firmware Memory Corruption in LED Flash Commands
- CVE-2026-21384MEDIUMQualcomm Memory Corruption in FastConnect & QCA Firmware
- CVE-2025-59605HIGHQualcomm Memory Corruption in Device Identifier Processing
- CVE-2025-10238MEDIUMThinkPad BIOS Out-of-Bounds Write, SMM Code Execution Risk
- CVE-2026-10114MEDIUMOpen5GS Out-of-Bounds Write in NF Profile Parser
- CVE-2026-10644MEDIUMZephyr SERCOM-G1 UART Out-of-Bounds Write on PIC32CM-JH