Possible race condition during async fastrpc session after sending RPC message due to the fastrpc ctx gets free during async session in Sna…

published 2021-02-22 5y ago modified 2026-06-17 4mo ago also EUVD-2020-3631

cvss: 7.4; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.1%; EPSS 0.1% chance of exploitation in 30 days, percentile 1%
public exploits: 0; none known

Possible race condition during async fastrpc session after sending RPC message due to the fastrpc ctx gets free during async session in Snapdragon Compute, Snapdragon Industrial IOT, Snapdragon Mobile

Is CVE-2020-11277 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.12% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	7.4	CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	6.9	AV:L/AC:M/Au:N/C:C/I:C/A:C

Affected products

Qualcomm, Inc. Snapdragon Compute, Snapdragon Industrial IOT, Snapdragon Mobile

Classification

Weakness

CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization
CWE-416 Use After Free

References

qualcomm.com /company/product-security/bulletins/february-2021-bulletin
vendor-advisory

Sources

CVE List CVE-2020-11277
NVD CVE-2020-11277

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.