NVD / CVE Program· CNA qualcomm

CVE-2024-33055: Use After Free in Computer Vision

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.10% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Memory corruption while invoking IOCTL calls to unmap the DMA buffers.

HighCVSS 7.8 · v3.1—No exploit No fix recorded

Memory safety

Published: Jan 6, 2025
Updated: Jun 17, 2026
EPSS: 0.1% · 0th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.8
CNA · qualcomm: 6.7; 1.1 point gap

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
qualcomm	sa8195p	cpe:2.3:h:qualcomm:sa8195p
qualcomm	fastconnect 6900 firmware	cpe:2.3:o:qualcomm:fastconnect_6900_firmware
qualcomm	fastconnect 6900	cpe:2.3:h:qualcomm:fastconnect_6900
qualcomm	fastconnect 7800 firmware	cpe:2.3:o:qualcomm:fastconnect_7800_firmware
qualcomm	fastconnect 7800	cpe:2.3:h:qualcomm:fastconnect_7800
qualcomm	qam8295p firmware	cpe:2.3:o:qualcomm:qam8295p_firmware
qualcomm	qam8295p	cpe:2.3:h:qualcomm:qam8295p
qualcomm	qca6574au firmware	cpe:2.3:o:qualcomm:qca6574au_firmware
qualcomm	qca6574au	cpe:2.3:h:qualcomm:qca6574au
qualcomm	qca6696 firmware	cpe:2.3:o:qualcomm:qca6696_firmware
qualcomm	qca6696	cpe:2.3:h:qualcomm:qca6696
qualcomm	qcm8550 firmware	cpe:2.3:o:qualcomm:qcm8550_firmware

and 66 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

qualcomm fastconnect 6900 firmwareall versions
qualcomm fastconnect 7800 firmwareall versions
qualcomm qam8295p firmwareall versions
qualcomm qca6574au firmwareall versions
qualcomm qca6696 firmwareall versions
qualcomm qcm8550 firmwareall versions
qualcomm qcs6490 firmwareall versions
qualcomm qcs8550 firmwareall versions
qualcomm sa6145p firmwareall versions
qualcomm sa6150p firmwareall versions
qualcomm sa6155p firmwareall versions
qualcomm sa8145p firmwareall versions
qualcomm sa8150p firmwareall versions
qualcomm sa8155p firmwareall versions
qualcomm sa8195p firmwareall versions
qualcomm sa8295p firmwareall versions
qualcomm sd 8 gen1 5g firmwareall versions
qualcomm sg8275p firmwareall versions
qualcomm sm8550p firmwareall versions
qualcomm snapdragon 8 gen 2 mobile firmwareall versions

Versions reported by the vendor

Affected version ranges reported by the assigning authority (qualcomm). Independent of NVD's CPE analysis and usually ahead of it.

Qualcomm, Inc. Snapdragon
- FastConnect 6900, FastConnect 7800, QAM8295P, QCA6574AU, QCA6696, QCM8550, QCS6490, QCS8550, Qualcomm Video Collaboration VC3 Platform, SA6145P, SA6150P, SA6155P … (+27)affected

Same product

qualcomm: all records

Other highest-scoring records for the same primary product.

CVE-2025-27034Improper Validation of Array Index in Multi-Mode Call Processor
39Monitor
CVE-2025-47405Untrusted Pointer Dereference in Camera
31Monitor
CVE-2025-47358Use After Free in Secure Processor
31Monitor

Published before and after this one in the same product

← EarlierCVE-2024-21460Jul 1, 2024 · Use of Insufficiently Random Values in Core
26Monitor
← EarlierCVE-2024-33041Jan 6, 2025 · Use of Out-of-range Pointer Offset in Computer Vision
31Monitor
Later →CVE-2024-33059Jan 6, 2025 · Use After Free in Computer Vision
31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2024-330590 days apartUse After Free in Computer Vision
31Monitor
CVE-2024-3841128 days apartUse After Free in Computer Vision
31Monitor
CVE-2024-4306156 days apartUse After Free in Audio
31Monitor
CVE-2024-4306256 days apartUse After Free in Camera Linux
31Monitor
CVE-2024-4558056 days apartUse After Free in DSP Service
31Monitor
CVE-2024-45567120 days apartUse After Free in Camera Driver
31Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

docs.qualcomm.com/product/publicresources/securitybulletin/january-2025-bulletin.html

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records