CVE-2021-30263

Possible race condition can occur due to lack of synchronization mechanism when On-Device Logging node open twice concurrently in Snapdragon Compute, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music

Published: 2021-11-12 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2021-30263 is rated Low Risk (28.3/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.14%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2021-30263

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.04% 0.14% +0.10%
2 2025-03-30 0.08% 0.04% -0.04%
3 2025-03-29 — 0.08% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2021-30263

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.7 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 0.8 5.9 [email protected]
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]
4.4 2.0 MEDIUM
AV:L/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 3.4 6.4 [email protected]

Weakness enumeration for CVE-2021-30263

Affected software / configurations for CVE-2021-30263

Vendor Product Version Raw CPE
qualcomm aqt1000_firmware — cpe:2.3:o:qualcomm:aqt1000_firmware:-:*:*:*:*:*:*:*
qualcomm ar8031_firmware — cpe:2.3:o:qualcomm:ar8031_firmware:-:*:*:*:*:*:*:*
qualcomm ar8035_firmware — cpe:2.3:o:qualcomm:ar8035_firmware:-:*:*:*:*:*:*:*
qualcomm csra6620_firmware — cpe:2.3:o:qualcomm:csra6620_firmware:-:*:*:*:*:*:*:*
qualcomm csra6640_firmware — cpe:2.3:o:qualcomm:csra6640_firmware:-:*:*:*:*:*:*:*
qualcomm qca6391_firmware — cpe:2.3:o:qualcomm:qca6391_firmware:-:*:*:*:*:*:*:*
qualcomm qca6420_firmware — cpe:2.3:o:qualcomm:qca6420_firmware:-:*:*:*:*:*:*:*
qualcomm qca6430_firmware — cpe:2.3:o:qualcomm:qca6430_firmware:-:*:*:*:*:*:*:*
qualcomm qca8337_firmware — cpe:2.3:o:qualcomm:qca8337_firmware:-:*:*:*:*:*:*:*
qualcomm qcm6125_firmware — cpe:2.3:o:qualcomm:qcm6125_firmware:-:*:*:*:*:*:*:*
qualcomm qcs405_firmware — cpe:2.3:o:qualcomm:qcs405_firmware:-:*:*:*:*:*:*:*
qualcomm qcs6125_firmware — cpe:2.3:o:qualcomm:qcs6125_firmware:-:*:*:*:*:*:*:*
qualcomm sd_8c_firmware — cpe:2.3:o:qualcomm:sd_8c_firmware:-:*:*:*:*:*:*:*
qualcomm sd_8cx_firmware — cpe:2.3:o:qualcomm:sd_8cx_firmware:-:*:*:*:*:*:*:*
qualcomm sd855_firmware — cpe:2.3:o:qualcomm:sd855_firmware:-:*:*:*:*:*:*:*
qualcomm sdx55_firmware — cpe:2.3:o:qualcomm:sdx55_firmware:-:*:*:*:*:*:*:*
qualcomm sdx55m_firmware — cpe:2.3:o:qualcomm:sdx55m_firmware:-:*:*:*:*:*:*:*
qualcomm wcd9335_firmware — cpe:2.3:o:qualcomm:wcd9335_firmware:-:*:*:*:*:*:*:*
qualcomm wcd9340_firmware — cpe:2.3:o:qualcomm:wcd9340_firmware:-:*:*:*:*:*:*:*
qualcomm wcd9341_firmware — cpe:2.3:o:qualcomm:wcd9341_firmware:-:*:*:*:*:*:*:*
qualcomm wcd9370_firmware — cpe:2.3:o:qualcomm:wcd9370_firmware:-:*:*:*:*:*:*:*
qualcomm wcn3950_firmware — cpe:2.3:o:qualcomm:wcn3950_firmware:-:*:*:*:*:*:*:*
qualcomm wcn3980_firmware — cpe:2.3:o:qualcomm:wcn3980_firmware:-:*:*:*:*:*:*:*
qualcomm wcn3998_firmware — cpe:2.3:o:qualcomm:wcn3998_firmware:-:*:*:*:*:*:*:*
qualcomm wcn3999_firmware — cpe:2.3:o:qualcomm:wcn3999_firmware:-:*:*:*:*:*:*:*
qualcomm wsa8810_firmware — cpe:2.3:o:qualcomm:wsa8810_firmware:-:*:*:*:*:*:*:*
qualcomm wsa8815_firmware — cpe:2.3:o:qualcomm:wsa8815_firmware:-:*:*:*:*:*:*:*

References for CVE-2021-30263

cvelogic Threat Intelligence