Snapdragon Compute, Snapdragon Connectivity…: Use After Free
CVE-2022-22090 is a high-severity use after free vulnerability in Snapdragon Compute, Snapdragon Connectivity, 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.16% 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 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 Mobile | Not specified in the record | Not stated |
| Qualcomm | Sd 8 Gen1 5g Firmware | Not specified in the record | Not stated |
| Qualcomm | Sd865 5g Firmware | Not specified in the record | Not stated |
| Qualcomm | Sd888 5g Firmware | Not specified in the record | Not stated |
| Qualcomm | Sdx65 Firmware | Not specified in the record | Not stated |
| Qualcomm | Sm7450 Firmware | Not specified in the record | Not stated |
| Qualcomm | Sm8475 Firmware | Not specified in the record | Not stated |
| Qualcomm | Sm8475p Firmware | Not specified in the record | Not stated |
| Qualcomm | Wcd9370 Firmware | Not specified in the record | Not stated |
| Qualcomm | Wcd9375 Firmware | Not specified in the record | Not stated |
| Qualcomm | Wcd9380 Firmware | Not specified in the record | Not stated |
| Qualcomm | Wcd9385 Firmware | Not specified in the record | Not stated |
| Qualcomm | Wcn6750 Firmware | Not specified in the record | Not stated |
| Qualcomm | Wcn6850 Firmware | Not specified in the record | Not stated |
| Qualcomm | Wcn6851 Firmware | Not specified in the record | Not stated |
| Qualcomm | Wcn6855 Firmware | Not specified in the record | Not stated |
| Qualcomm | Wcn6856 Firmware | Not specified in the record | Not stated |
| Qualcomm | Wcn7850 Firmware | Not specified in the record | Not stated |
| Qualcomm | Wcn7851 Firmware | Not specified in the record | Not stated |
| Qualcomm | Wsa8810 Firmware | Not specified in the record | Not stated |
| Qualcomm | Wsa8815 Firmware | Not specified in the record | Not stated |
| Qualcomm | Wsa8830 Firmware | Not specified in the record | Not stated |
| Qualcomm | Wsa8832 Firmware | Not specified in the record | Not stated |
| Qualcomm | Wsa8835 Firmware | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. 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 |
| CVSS 2.0 | 7.2 | High | NVD |
Official description
Memory corruption in audio due to use after free while managing buffers from internal cache in Snapdragon Compute, Snapdragon Connectivity, 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
Recent Use After Free vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.5 High severity
- 7.5 High severity
- 7.8 High severity
Spotted an error? Tell us.