Snapdragon Auto, Snapdragon Compute…: Missing Release of Memory after Effective Lifetime
CVE-2022-22067 is a high-severity missing release of memory after effective lifetime vulnerability in Snapdragon Auto, 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.3% 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 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 Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Mobile | Not specified in the record | Not stated |
| Qualcomm | Ar8035 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 | Qca6421 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6426 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6431 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6436 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6574a Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6574au Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6595au Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6696 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca8081 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca8337 Firmware | Not specified in the record | Not stated |
| Qualcomm | Sa515m Firmware | Not specified in the record | Not stated |
| Qualcomm | Sd 8 Gen1 5g Firmware | Not specified in the record | Not stated |
| Qualcomm | Sd480 Firmware | Not specified in the record | Not stated |
| Qualcomm | Sd690 5g Firmware | Not specified in the record | Not stated |
| Qualcomm | Sd695 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 | Sd778g Firmware | Not specified in the record | Not stated |
| Qualcomm | Sd780g 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 | 7.5 | High | CNA (qualcomm.com) |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
Potential memory leak in modem during the processing of NSA RRC Reconfiguration with invalid Radio Bearer Config in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Mobile
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Release of Memory after Effective Lifetime
The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
How developers prevent this class of flaw
- Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone. For example, glibc in Linux provides protection against free of invalid pointers. When using Xcode to target OS X or iOS, enable automatic reference counting (ARC). To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std
- Use an abstraction library to abstract away risky APIs. Not a complete solution.
- Consider using the Boehm-Demers-Weiser garbage collector (bdwgc), which can help avoid leaks.
More Missing Release of Memory after Effective Lifetime vulnerabilities (CWE-401)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Recent Missing Release of Memory after Effective Lifetime vulnerabilities
- 8.2 High severity
- 7.8 High severity
- 7.1 High severity
- 7.5 High severity
- 7.5 High severity
- 7.1 High severity
Spotted an error? Tell us.