Snapdragon Auto, Snapdragon Compute…: Use After Free
CVE-2022-25677 is a high-severity use after free vulnerability in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking 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 Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking versions: APQ8096AU; AQT1000; AR9380, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.13% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on qualcomm.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Qualcomm | Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking | APQ8096AU; AQT1000; AR9380; CSR8811; IPQ4018; IPQ4019; IPQ4028; IPQ4029; and 32 more ranges | Not stated |
| Qualcomm | Apq8096au Firmware | Not specified in the record | Not stated |
| Qualcomm | Aqt1000 Firmware | Not specified in the record | Not stated |
| Qualcomm | Ar9380 Firmware | Not specified in the record | Not stated |
| Qualcomm | Csr8811 Firmware | Not specified in the record | Not stated |
| Qualcomm | Ipq4018 Firmware | Not specified in the record | Not stated |
| Qualcomm | Ipq4019 Firmware | Not specified in the record | Not stated |
| Qualcomm | Ipq4028 Firmware | Not specified in the record | Not stated |
| Qualcomm | Ipq4029 Firmware | Not specified in the record | Not stated |
| Qualcomm | Ipq5010 Firmware | Not specified in the record | Not stated |
| Qualcomm | Ipq5018 Firmware | Not specified in the record | Not stated |
| Qualcomm | Ipq5028 Firmware | Not specified in the record | Not stated |
| Qualcomm | Ipq6000 Firmware | Not specified in the record | Not stated |
| Qualcomm | Ipq6010 Firmware | Not specified in the record | Not stated |
| Qualcomm | Ipq6018 Firmware | Not specified in the record | Not stated |
| Qualcomm | Ipq6028 Firmware | Not specified in the record | Not stated |
| Qualcomm | Ipq8064 Firmware | Not specified in the record | Not stated |
| Qualcomm | Ipq8065 Firmware | Not specified in the record | Not stated |
| Qualcomm | Ipq8068 Firmware | Not specified in the record | Not stated |
| Qualcomm | Ipq8070 Firmware | Not specified in the record | Not stated |
| Qualcomm | Ipq8070a Firmware | Not specified in the record | Not stated |
| Qualcomm | Ipq8071a Firmware | Not specified in the record | Not stated |
| Qualcomm | Ipq8072a Firmware | Not specified in the record | Not stated |
| Qualcomm | Ipq8074a Firmware | Not specified in the record | Not stated |
| Qualcomm | Ipq8076 Firmware | Not specified in the record | Not 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 NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 6.7 | Medium | CNA (qualcomm.com) |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
Memory corruption in diag due to use after free while processing dci packet in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.
How developers prevent this class of flaw
- Choose a language that provides automatic memory management.
- When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking
- 8.1 High severity
- 7.8 High severity
- 7.5 High severity
- 7.8 High severity
- 7.0 High severity
- 7.8 High severity
Recent Use After Free vulnerabilities
- 7.8 High severity
- 8.8 High severity
- 7.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
Spotted an error? Tell us.