NVD / CVE Program· CNA qualcomm

CVE-2025-21437: Use After Free in Automotive Linux OS

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

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 processing memory map or unmap IOCTL operations simultaneously.

Memory safety

Published: Apr 7, 2025
Updated: Jun 17, 2026
EPSS: 0.1% · 1th 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: —
CNA · qualcomm: 7.8; NVD has not scored this yet; the score shown is the CNA’s.

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.

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	qam8255p firmware	cpe:2.3:o:qualcomm:qam8255p_firmware
qualcomm	qam8255p	cpe:2.3:h:qualcomm:qam8255p
qualcomm	qam8295p firmware	cpe:2.3:o:qualcomm:qam8295p_firmware
qualcomm	qam8295p	cpe:2.3:h:qualcomm:qam8295p
qualcomm	qam8620p firmware	cpe:2.3:o:qualcomm:qam8620p_firmware
qualcomm	qam8620p	cpe:2.3:h:qualcomm:qam8620p
qualcomm	qam8650p firmware	cpe:2.3:o:qualcomm:qam8650p_firmware
qualcomm	qam8650p	cpe:2.3:h:qualcomm:qam8650p
qualcomm	qam8775p firmware	cpe:2.3:o:qualcomm:qam8775p_firmware
qualcomm	qam8775p	cpe:2.3:h:qualcomm:qam8775p
qualcomm	qamsrv1h firmware	cpe:2.3:o:qualcomm:qamsrv1h_firmware
qualcomm	qamsrv1h	cpe:2.3:h:qualcomm:qamsrv1h

and 50 more

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
- QAM8255P, QAM8295P, QAM8620P, QAM8650P, QAM8775P, QAMSRV1H, QAMSRV1M, QCA6574, QCA6574A, QCA6574AU, QCA6595, QCA6595AU … (+19)affected

Affected versions · NVD (20)

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

qualcomm qam8255p firmwareall versions
qualcomm qam8295p firmwareall versions
qualcomm qam8620p firmwareall versions
qualcomm qam8650p firmwareall versions
qualcomm qam8775p firmwareall versions
qualcomm qamsrv1h firmwareall versions
qualcomm qamsrv1m firmwareall versions
qualcomm qca6574 firmwareall versions
qualcomm qca6574a firmwareall versions
qualcomm qca6574au firmwareall versions
qualcomm qca6595 firmwareall versions
qualcomm qca6595au firmwareall versions
qualcomm qca6688aq firmwareall versions
qualcomm qca6696 firmwareall versions
qualcomm qca6698aq firmwareall versions
qualcomm qca6797aq firmwareall versions
qualcomm sa6155p firmwareall versions
qualcomm sa7255p firmwareall versions
qualcomm sa7775p firmwareall versions
qualcomm sa8155p firmwareall versions

Same product

qualcomm: all records

Other highest-scoring records for the same primary product.

CVE-2024-53029Improper Input Validation in Automotive OS Platform
35Monitor
CVE-2025-47372Buffer Copy Without Checking Size of Input in Boot
33Monitor
CVE-2024-33035Integer Overflow or Wraparound in Display
33Monitor

Published before and after this one in the same product

← EarlierCVE-2025-21425Apr 7, 2025 · Improper Access Control in Automotive Linux OS
31Monitor
← EarlierCVE-2025-21431Apr 7, 2025 · Time-of-check Time-of-use (TOCTOU) Race Condition in Automotive OS Platform
18Monitor
Later →CVE-2025-21442Apr 7, 2025 · Integer Overflow to Buffer Overflow in Automotive Vehicle Networks
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.

Variant candidates

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

CVE-2025-27077170 days apartUse After Free in Automotive Software platform based on QNX
31Monitor
CVE-2025-47315170 days apartUse After Free in Automotive Software platform based on QNX
31Monitor
CVE-2023-33108461 days apartUse After Free in Graphics
31Monitor
CVE-2023-43543308 days apartUse After Free in Audio
28Monitor
CVE-2024-498480 days apartUse After Free in DSP Service
26Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

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-secondary

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 (0)

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

References

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

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

All records