Snapdragon Compute, Snapdragon Connectivity…: Use After Free
CVE-2022-22095 is a high-severity use after free vulnerability in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile 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. There is no confirmed exploitation so far. EPSS estimates a 0.12% 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 Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile 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 Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile | Not specified in the record | Not stated |
| Qualcomm | Apq8053 Firmware | Not specified in the record | Not stated |
| Qualcomm | Msm8953 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6390 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6391 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6426 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6436 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qcm2290 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qcm4290 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qcs2290 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qcs4290 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qrb5165 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qrb5165m Firmware | Not specified in the record | Not stated |
| Qualcomm | Qrb5165n Firmware | Not specified in the record | Not stated |
| Qualcomm | Sd439 Firmware | Not specified in the record | Not stated |
| Qualcomm | Sd460 Firmware | Not specified in the record | Not stated |
| Qualcomm | Sd662 Firmware | Not specified in the record | Not stated |
| Qualcomm | Sd680 Firmware | Not specified in the record | Not stated |
| Qualcomm | Sd690 5g Firmware | Not specified in the record | Not stated |
| Qualcomm | Sd750g Firmware | Not specified in the record | Not stated |
| Qualcomm | Sd765 Firmware | Not specified in the record | Not stated |
| Qualcomm | Sd765g Firmware | Not specified in the record | Not stated |
| Qualcomm | Sd768g Firmware | Not specified in the record | Not stated |
| Qualcomm | Sd855 Firmware | Not specified in the record | Not stated |
| Qualcomm | Sd865 5g Firmware | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE; 25 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 | 8.4 | High | CNA (qualcomm.com) |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
Memory corruption in synx driver due to use-after-free condition in the synx driver due to accessing object handles without acquiring lock in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile
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.
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile
- 7.0 High severity
- 7.0 High severity
Recent Use After Free vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.