CyberSecBulletin
CVE-2022-22057NVD status: Modified

Snapdragon Auto, Snapdragon Compute…: Concurrent Execution using Shared Resource with Improper Synchronization

Published Updated By the CyberSecBulletin desk

CVE-2022-22057 is a high-severity concurrent execution using shared resource with improper synchronization 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.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.44% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. 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.
  2. Read the advisory on qualcomm.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
QualcommSnapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon WearablesNot specified in the recordNot stated
QualcommApq8053 FirmwareNot specified in the recordNot stated
QualcommAr8035 FirmwareNot specified in the recordNot stated
QualcommMsm8953 FirmwareNot specified in the recordNot stated
QualcommQca6174a FirmwareNot specified in the recordNot stated
QualcommQca6390 FirmwareNot specified in the recordNot stated
QualcommQca6391 FirmwareNot specified in the recordNot stated
QualcommQca6426 FirmwareNot specified in the recordNot stated
QualcommQca6436 FirmwareNot specified in the recordNot stated
QualcommQca6595au FirmwareNot specified in the recordNot stated
QualcommQca8081 FirmwareNot specified in the recordNot stated
QualcommQca8337 FirmwareNot specified in the recordNot stated
QualcommQca9377 FirmwareNot specified in the recordNot stated
QualcommQcm2290 FirmwareNot specified in the recordNot stated
QualcommQcm4290 FirmwareNot specified in the recordNot stated
QualcommQcm6490 FirmwareNot specified in the recordNot stated
QualcommQcs2290 FirmwareNot specified in the recordNot stated
QualcommQcs4290 FirmwareNot specified in the recordNot stated
QualcommQcs6490 FirmwareNot specified in the recordNot stated
QualcommQrb5165 FirmwareNot specified in the recordNot stated
QualcommQrb5165m FirmwareNot specified in the recordNot stated
QualcommQrb5165n FirmwareNot specified in the recordNot stated
QualcommQualcomm215 FirmwareNot specified in the recordNot stated
QualcommSa6155p FirmwareNot specified in the recordNot stated
QualcommSa8155p FirmwareNot specified in the recordNot 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 systemScoreSeverityScored by
CVSS 3.18.4HighCNA (qualcomm.com)
CVSS 3.17.8HighNVD
CVSS 2.07.2HighNVD

Official description

Use after free in graphics fence due to a race condition while closing fence file descriptor and destroy graphics timeline simultaneously 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: Concurrent Execution using Shared Resource with Improper Synchronization

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

How developers prevent this class of flaw

  • In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.
  • Use thread-safe capabilities such as the data access abstraction in Spring.
  • Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring. Additionally, this will minimize the amount of synchronization necessary and may even help to reduce the likelihood of a denial of service where an attacker may be able to repeatedly trigger a critical section (CWE-400).

More Concurrent Execution using Shared Resource with Improper Synchronization vulnerabilities (CWE-362)

Timeline

  1. CVE record published.
  2. 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

All Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables vulnerabilities

Recent Concurrent Execution using Shared Resource with Improper Synchronization vulnerabilities

Spotted an error? Tell us.