CVE-2022-33278 | Buffer copy without checking the size of input in HLOS

Memory corruption due to buffer copy without checking the size of input in HLOS when input message size is larger than the buffer capacity.

Published: 2023-03-10 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-33278 is rated Low Risk (36.7/100): CVSS High severity, with low exploitation likelihood (EPSS 0.05%). 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-2022-33278

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 2025-11-21 0.05% 0.05% +0.00%
2 2025-11-18 0.07% 0.05% -0.02%
3 2025-03-17 — 0.07% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-33278

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
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]
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]

Weakness enumeration for CVE-2022-33278

Affected software / configurations for CVE-2022-33278

Vendor Product Version Raw CPE
qualcomm aqt1000_firmware — cpe:2.3:o:qualcomm:aqt1000_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 qam8295p_firmware — cpe:2.3:o:qualcomm:qam8295p_firmware:-:*:*:*:*:*:*:*
qualcomm qca6390_firmware — cpe:2.3:o:qualcomm:qca6390_firmware:-:*:*:*:*:*:*:*
qualcomm qca6391_firmware — cpe:2.3:o:qualcomm:qca6391_firmware:-:*:*:*:*:*:*:*
qualcomm qca6420_firmware — cpe:2.3:o:qualcomm:qca6420_firmware:-:*:*:*:*:*:*:*
qualcomm qca6421_firmware — cpe:2.3:o:qualcomm:qca6421_firmware:-:*:*:*:*:*:*:*
qualcomm qca6426_firmware — cpe:2.3:o:qualcomm:qca6426_firmware:-:*:*:*:*:*:*:*
qualcomm qca6430_firmware — cpe:2.3:o:qualcomm:qca6430_firmware:-:*:*:*:*:*:*:*
qualcomm qca6431_firmware — cpe:2.3:o:qualcomm:qca6431_firmware:-:*:*:*:*:*:*:*
qualcomm qca6436_firmware — cpe:2.3:o:qualcomm:qca6436_firmware:-:*:*:*:*:*:*:*
qualcomm qca6574_firmware — cpe:2.3:o:qualcomm:qca6574_firmware:-:*:*:*:*:*:*:*
qualcomm qca6574a_firmware — cpe:2.3:o:qualcomm:qca6574a_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 qca6696_firmware — cpe:2.3:o:qualcomm:qca6696_firmware:-:*:*:*:*:*:*:*
qualcomm qca6698aq_firmware — cpe:2.3:o:qualcomm:qca6698aq_firmware:-:*:*:*:*:*:*:*
qualcomm qca8081_firmware — cpe:2.3:o:qualcomm:qca8081_firmware:-:*:*:*:*:*:*:*
qualcomm qca8337_firmware — cpe:2.3:o:qualcomm:qca8337_firmware:-:*:*:*:*:*:*:*
qualcomm qcc5100_firmware — cpe:2.3:o:qualcomm:qcc5100_firmware:-:*:*:*:*:*:*:*
qualcomm qcm2290_firmware — cpe:2.3:o:qualcomm:qcm2290_firmware:-:*:*:*:*:*:*:*
qualcomm qcm4290_firmware — cpe:2.3:o:qualcomm:qcm4290_firmware:-:*:*:*:*:*:*:*
qualcomm qcm6125_firmware — cpe:2.3:o:qualcomm:qcm6125_firmware:-:*:*:*:*:*:*:*
qualcomm qcm6490_firmware — cpe:2.3:o:qualcomm:qcm6490_firmware:-:*:*:*:*:*:*:*
qualcomm qcn6024_firmware — cpe:2.3:o:qualcomm:qcn6024_firmware:-:*:*:*:*:*:*:*
qualcomm qcn7606_firmware — cpe:2.3:o:qualcomm:qcn7606_firmware:-:*:*:*:*:*:*:*
qualcomm qcn9024_firmware — cpe:2.3:o:qualcomm:qcn9024_firmware:-:*:*:*:*:*:*:*
qualcomm qcs2290_firmware — cpe:2.3:o:qualcomm:qcs2290_firmware:-:*:*:*:*:*:*:*
qualcomm qcs405_firmware — cpe:2.3:o:qualcomm:qcs405_firmware:-:*:*:*:*:*:*:*
qualcomm qcs4290_firmware — cpe:2.3:o:qualcomm:qcs4290_firmware:-:*:*:*:*:*:*:*
qualcomm qcs6125_firmware — cpe:2.3:o:qualcomm:qcs6125_firmware:-:*:*:*:*:*:*:*
qualcomm qcs6490_firmware — cpe:2.3:o:qualcomm:qcs6490_firmware:-:*:*:*:*:*:*:*
qualcomm qsm8350_firmware — cpe:2.3:o:qualcomm:qsm8350_firmware:-:*:*:*:*:*:*:*
qualcomm sa4150p_firmware — cpe:2.3:o:qualcomm:sa4150p_firmware:-:*:*:*:*:*:*:*
qualcomm sa4155p_firmware — cpe:2.3:o:qualcomm:sa4155p_firmware:-:*:*:*:*:*:*:*
qualcomm sa6145p_firmware — cpe:2.3:o:qualcomm:sa6145p_firmware:-:*:*:*:*:*:*:*
qualcomm sa6150p_firmware — cpe:2.3:o:qualcomm:sa6150p_firmware:-:*:*:*:*:*:*:*
qualcomm sa6155_firmware — cpe:2.3:o:qualcomm:sa6155_firmware:-:*:*:*:*:*:*:*
qualcomm sa6155p_firmware — cpe:2.3:o:qualcomm:sa6155p_firmware:-:*:*:*:*:*:*:*
qualcomm sa8145p_firmware — cpe:2.3:o:qualcomm:sa8145p_firmware:-:*:*:*:*:*:*:*
qualcomm sa8150p_firmware — cpe:2.3:o:qualcomm:sa8150p_firmware:-:*:*:*:*:*:*:*
qualcomm sa8155_firmware — cpe:2.3:o:qualcomm:sa8155_firmware:-:*:*:*:*:*:*:*
qualcomm sa8155p_firmware — cpe:2.3:o:qualcomm:sa8155p_firmware:-:*:*:*:*:*:*:*
qualcomm sa8195p_firmware — cpe:2.3:o:qualcomm:sa8195p_firmware:-:*:*:*:*:*:*:*
qualcomm sa8295p_firmware — cpe:2.3:o:qualcomm:sa8295p_firmware:-:*:*:*:*:*:*:*
qualcomm sa8540p_firmware — cpe:2.3:o:qualcomm:sa8540p_firmware:-:*:*:*:*:*:*:*
qualcomm sa9000p_firmware — cpe:2.3:o:qualcomm:sa9000p_firmware:-:*:*:*:*:*:*:*
qualcomm sd_675_firmware — cpe:2.3:o:qualcomm:sd_675_firmware:-:*:*:*:*:*:*:*
qualcomm sd_8_gen1_5g_firmware — cpe:2.3:o:qualcomm:sd_8_gen1_5g_firmware:-:*:*:*:*:*:*:*
qualcomm sd_8cx_gen3_firmware — cpe:2.3:o:qualcomm:sd_8cx_gen3_firmware:-:*:*:*:*:*:*:*
qualcomm sd460_firmware — cpe:2.3:o:qualcomm:sd460_firmware:-:*:*:*:*:*:*:*
qualcomm sd480_firmware — cpe:2.3:o:qualcomm:sd480_firmware:-:*:*:*:*:*:*:*
qualcomm sd662_firmware — cpe:2.3:o:qualcomm:sd662_firmware:-:*:*:*:*:*:*:*
qualcomm sd665_firmware — cpe:2.3:o:qualcomm:sd665_firmware:-:*:*:*:*:*:*:*
qualcomm sd670_firmware — cpe:2.3:o:qualcomm:sd670_firmware:-:*:*:*:*:*:*:*
qualcomm sd675_firmware — cpe:2.3:o:qualcomm:sd675_firmware:-:*:*:*:*:*:*:*
qualcomm sd678_firmware — cpe:2.3:o:qualcomm:sd678_firmware:-:*:*:*:*:*:*:*
qualcomm sd680_firmware — cpe:2.3:o:qualcomm:sd680_firmware:-:*:*:*:*:*:*:*
qualcomm sd690_5g_firmware — cpe:2.3:o:qualcomm:sd690_5g_firmware:-:*:*:*:*:*:*:*
qualcomm sd695_firmware — cpe:2.3:o:qualcomm:sd695_firmware:-:*:*:*:*:*:*:*
qualcomm sd710_firmware — cpe:2.3:o:qualcomm:sd710_firmware:-:*:*:*:*:*:*:*
qualcomm sd720g_firmware — cpe:2.3:o:qualcomm:sd720g_firmware:-:*:*:*:*:*:*:*
qualcomm sd730_firmware — cpe:2.3:o:qualcomm:sd730_firmware:-:*:*:*:*:*:*:*
qualcomm sd750g_firmware — cpe:2.3:o:qualcomm:sd750g_firmware:-:*:*:*:*:*:*:*
qualcomm sd765_firmware — cpe:2.3:o:qualcomm:sd765_firmware:-:*:*:*:*:*:*:*
qualcomm sd765g_firmware — cpe:2.3:o:qualcomm:sd765g_firmware:-:*:*:*:*:*:*:*
qualcomm sd768g_firmware — cpe:2.3:o:qualcomm:sd768g_firmware:-:*:*:*:*:*:*:*
qualcomm sd778g_firmware — cpe:2.3:o:qualcomm:sd778g_firmware:-:*:*:*:*:*:*:*
qualcomm sd780g_firmware — cpe:2.3:o:qualcomm:sd780g_firmware:-:*:*:*:*:*:*:*
qualcomm sd855_firmware — cpe:2.3:o:qualcomm:sd855_firmware:-:*:*:*:*:*:*:*
qualcomm sd865_5g_firmware — cpe:2.3:o:qualcomm:sd865_5g_firmware:-:*:*:*:*:*:*:*
qualcomm sd870_firmware — cpe:2.3:o:qualcomm:sd870_firmware:-:*:*:*:*:*:*:*
qualcomm sd888_firmware — cpe:2.3:o:qualcomm:sd888_firmware:-:*:*:*:*:*:*:*
qualcomm sd888_5g_firmware — cpe:2.3:o:qualcomm:sd888_5g_firmware:-:*:*:*:*:*:*:*
qualcomm sdx50m_firmware — cpe:2.3:o:qualcomm:sdx50m_firmware:-:*:*:*:*:*:*:*
qualcomm sdx55m_firmware — cpe:2.3:o:qualcomm:sdx55m_firmware:-:*:*:*:*:*:*:*
qualcomm sdx65_firmware — cpe:2.3:o:qualcomm:sdx65_firmware:-:*:*:*:*:*:*:*

References for CVE-2022-33278

cvelogic Threat Intelligence