Snapdragon Auto, Snapdragon Compute…: Time-of-check Time-of-use (TOCTOU) Race Condition
CVE-2022-25696 is a high-severity time-of-check time-of-use (TOCTOU) race condition vulnerability in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables from Qualcomm, with a CVSS 3.1 base score of 7.0 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.09% 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 Industrial IOT, Snapdragon Mobile, Snapdragon Wearables 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 Industrial IOT, Snapdragon Mobile, Snapdragon Wearables | Not specified in the record | Not stated |
| Qualcomm | Apq8053 Firmware | Not specified in the record | Not stated |
| Qualcomm | Aqt1000 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 | Qca6420 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6430 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6574 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 | Qcm2290 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qcm4290 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qcm6490 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 | Qcs6490 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qualcomm215 Firmware | Not specified in the record | Not stated |
| Qualcomm | Sa6155p Firmware | Not specified in the record | Not stated |
| Qualcomm | Sa8155p Firmware | Not specified in the record | Not stated |
| Qualcomm | Sa8195p Firmware | Not specified in the record | Not stated |
| Qualcomm | Sd 675 Firmware | Not specified in the record | Not stated |
| Qualcomm | Sd 8 Gen1 5g 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
- HighSuccess depends on conditions outside the attacker's control.
- 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:H/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.0 | High | NVD |
Official description
Memory corruption in display due to time-of-check time-of-use race condition during map or unmap in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Time-of-check Time-of-use (TOCTOU) Race Condition
The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.
How developers prevent this class of flaw
- The most basic advice for TOCTOU vulnerabilities is to not perform a check before the use. This does not resolve the underlying issue of the execution of a function on a resource whose state and identity cannot be assured, but it does help to limit the false sense of security given by the check.
- When the file being altered is owned by the current user and group, set the effective gid and uid to that of the current user and group when executing this statement.
- Limit the interleaving of operations on files from multiple processes.
More Time-of-check Time-of-use (TOCTOU) Race Condition vulnerabilities (CWE-367)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables
- 9.8 Critical severity
- 7.8 High severity
- 9.8 Critical severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Recent Time-of-check Time-of-use (TOCTOU) Race Condition vulnerabilities
- 7.0 High severity
- 7.0 High severity
- 7.0 High severity
- 7.8 High severity
- 7.0 High severity
- 7.0 High severity
Spotted an error? Tell us.