CyberSecBulletin
CVE-2026-21385Exploited in the wildNVD status: Analyzed

Qualcomm Multiple Chipsets Memory Corruption

CVE-2026-21385 is a high-severity integer overflow or wraparound vulnerability in Snapdragon from Qualcomm, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected Snapdragon versions: 5G Fixed Wireless Access Platform; APQ8098; AR8031, and others listed below. The record does not name a fixed version, so check the vendor advisory. CISA added it to the Known Exploited Vulnerabilities catalogue on March 3, 2026, which means attacks have been observed in the wild.

Patch now

Attackers are already exploiting this vulnerability, according to CISA.

What to do

  1. Check which version of Snapdragon you run against the affected versions below, and install the vendor's latest release.
  2. CISA's required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
  3. Read the advisory on docs.qualcomm.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
QualcommSnapdragon5G Fixed Wireless Access Platform; APQ8098; AR8031; AR8035; C-V2X 9150; CSRA6620; CSRA6640; FastConnect 6200; and 32 more rangesNot stated
QualcommSm7675p FirmwareNot specified in the recordNot stated
QualcommSm8475p FirmwareNot specified in the recordNot stated
QualcommSm8550p FirmwareNot specified in the recordNot stated
QualcommSm8635 FirmwareNot specified in the recordNot stated
QualcommSm8635p FirmwareNot specified in the recordNot stated
QualcommSm8650q FirmwareNot specified in the recordNot stated
QualcommSm8750p FirmwareNot specified in the recordNot stated
QualcommSmart Audio 400 Platform FirmwareNot specified in the recordNot stated
QualcommSmart Display 200 Platform FirmwareNot specified in the recordNot stated
QualcommSnapdragon 4 Gen 1 Mobile Platform FirmwareNot specified in the recordNot stated
QualcommSnapdragon 4 Gen 2 Mobile Platform FirmwareNot specified in the recordNot stated
QualcommSnapdragon 429 Mobile Platform FirmwareNot specified in the recordNot stated
QualcommSnapdragon 460 Mobile Platform FirmwareNot specified in the recordNot stated
QualcommSnapdragon 480+ 5g Mobile Platform FirmwareNot specified in the recordNot stated
QualcommSnapdragon 6 Gen 1 Mobile Platform FirmwareNot specified in the recordNot stated
QualcommSnapdragon 6 Gen 3 Mobile Platform FirmwareNot specified in the recordNot stated
QualcommSnapdragon 6 Gen 4 Mobile Platform FirmwareNot specified in the recordNot stated
QualcommSnapdragon 625 Mobile Platform FirmwareNot specified in the recordNot stated
QualcommSnapdragon 626 Mobile Platform FirmwareNot specified in the recordNot stated
QualcommSnapdragon 660 Mobile Platform FirmwareNot specified in the recordNot stated
QualcommSnapdragon 662 Mobile Platform FirmwareNot specified in the recordNot stated
QualcommSnapdragon 680 4g Mobile Platform FirmwareNot specified in the recordNot stated
QualcommSnapdragon 685 4g Mobile Platform FirmwareNot specified in the recordNot stated
QualcommSnapdragon 690 5g Mobile Platform FirmwareNot specified in the recordNot stated

Version data comes from the organisation that assigned the CVE; 35 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (qualcomm.com).

Official description

Memory corruption while using alignments for memory allocation.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Integer Overflow or Wraparound

The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

How developers prevent this class of flaw

  • Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. If possible, choose a language or compiler that performs automatic bounds checking.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Use libraries or frameworks that make it easier to handle numbers without unexpected consequences. Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++).

More Integer Overflow or Wraparound vulnerabilities (CWE-190)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
  3. Added to CISA's Known Exploited Vulnerabilities catalogue.
  4. Deadline for US federal agencies to remediate, set by CISA.
  5. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Other vulnerabilities in Snapdragon

All Snapdragon vulnerabilities

Recent Integer Overflow or Wraparound vulnerabilities

Spotted an error? Tell us.