CVE-2024-43064 | Permissions, Privileges, and Access Controls issue in Automotive OS Platform

Uncontrolled resource consumption when a driver, an application or a SMMU client tries to access the global registers through SMMU.

Published: 2025-01-06 Last update: 2025-01-13 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-43064 is rated Low Risk (36.1/100): CVSS High severity, with low exploitation likelihood (EPSS 0.06%). 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-2024-43064

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-02-15 0.04% 0.06% +0.01%
2 2025-01-07 — 0.04% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-43064

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/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:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
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:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
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 6.0 [email protected]
4.7 3.1 MEDIUM
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/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:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
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:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.0 3.6 [email protected]

Weakness enumeration for CVE-2024-43064

Affected software / configurations for CVE-2024-43064

Vendor Product Version Raw CPE
qualcomm qam8255p_firmware — cpe:2.3:o:qualcomm:qam8255p_firmware:-:*:*:*:*:*:*:*
qualcomm qam8295p_firmware — cpe:2.3:o:qualcomm:qam8295p_firmware:-:*:*:*:*:*:*:*
qualcomm qam8620p_firmware — cpe:2.3:o:qualcomm:qam8620p_firmware:-:*:*:*:*:*:*:*
qualcomm qam8650p_firmware — cpe:2.3:o:qualcomm:qam8650p_firmware:-:*:*:*:*:*:*:*
qualcomm qam8775p_firmware — cpe:2.3:o:qualcomm:qam8775p_firmware:-:*:*:*:*:*:*:*
qualcomm qamsrv1h_firmware — cpe:2.3:o:qualcomm:qamsrv1h_firmware:-:*:*:*:*:*:*:*
qualcomm qamsrv1m_firmware — cpe:2.3:o:qualcomm:qamsrv1m_firmware:-:*:*:*:*:*:*:*
qualcomm qca6574au_firmware — cpe:2.3:o:qualcomm:qca6574au_firmware:-:*:*:*:*:*:*:*
qualcomm qca6595_firmware — cpe:2.3:o:qualcomm:qca6595_firmware:-:*:*:*:*:*:*:*
qualcomm qca6595au_firmware — cpe:2.3:o:qualcomm:qca6595au_firmware:-:*:*:*:*:*:*:*
qualcomm qca6688aq_firmware — cpe:2.3:o:qualcomm:qca6688aq_firmware:-:*:*:*:*:*:*:*
qualcomm qca6696_firmware — cpe:2.3:o:qualcomm:qca6696_firmware:-:*:*:*:*:*:*:*
qualcomm qca6698aq_firmware — cpe:2.3:o:qualcomm:qca6698aq_firmware:-:*:*:*:*:*:*:*
qualcomm sa7255p_firmware — cpe:2.3:o:qualcomm:sa7255p_firmware:-:*:*:*:*:*:*:*
qualcomm sa7775p_firmware — cpe:2.3:o:qualcomm:sa7775p_firmware:-:*:*:*:*:*:*:*
qualcomm sa8255p_firmware — cpe:2.3:o:qualcomm:sa8255p_firmware:-:*:*:*:*:*:*:*
qualcomm sa8295p_firmware — cpe:2.3:o:qualcomm:sa8295p_firmware:-:*:*:*:*:*:*:*
qualcomm sa8540p_firmware — cpe:2.3:o:qualcomm:sa8540p_firmware:-:*:*:*:*:*:*:*
qualcomm sa8620p_firmware — cpe:2.3:o:qualcomm:sa8620p_firmware:-:*:*:*:*:*:*:*
qualcomm sa8650p_firmware — cpe:2.3:o:qualcomm:sa8650p_firmware:-:*:*:*:*:*:*:*
qualcomm sa8770p_firmware — cpe:2.3:o:qualcomm:sa8770p_firmware:-:*:*:*:*:*:*:*
qualcomm sa8775p_firmware — cpe:2.3:o:qualcomm:sa8775p_firmware:-:*:*:*:*:*:*:*
qualcomm sa9000p_firmware — cpe:2.3:o:qualcomm:sa9000p_firmware:-:*:*:*:*:*:*:*
qualcomm sdm429w_firmware — cpe:2.3:o:qualcomm:sdm429w_firmware:-:*:*:*:*:*:*:*
qualcomm snapdragon_429_mobile_firmware — cpe:2.3:o:qualcomm:snapdragon_429_mobile_firmware:-:*:*:*:*:*:*:*
qualcomm srv1h_firmware — cpe:2.3:o:qualcomm:srv1h_firmware:-:*:*:*:*:*:*:*
qualcomm srv1l_firmware — cpe:2.3:o:qualcomm:srv1l_firmware:-:*:*:*:*:*:*:*
qualcomm srv1m_firmware — cpe:2.3:o:qualcomm:srv1m_firmware:-:*:*:*:*:*:*:*
qualcomm wcn3620_firmware — cpe:2.3:o:qualcomm:wcn3620_firmware:-:*:*:*:*:*:*:*
qualcomm wcn3660b_firmware — cpe:2.3:o:qualcomm:wcn3660b_firmware:-:*:*:*:*:*:*:*

References for CVE-2024-43064

cvelogic Threat Intelligence