CVE-2019-2293· NVD / CVE Program· CNA qualcomm

Pointer dereference while freeing IFE resources due to lack of length check of in port resource.

Pointer dereference while freeing IFE resources due to lack of length check of in port resource. in Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in MSM8909W, QCS405, QCS605, SD 425, SD 427, SD 430, SD 435, SD 450, SD 625, SD 636, SD 675, SD 712 / SD 710 / SD 670, SD 730, SD 845 / SD 850, SD 855, SDM630, SDM660, SDX24

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

Memory safety

Published: Jul 25, 2019
Updated: Jun 16, 2026
EPSS: 0.2% · 9th percentile
CWE: CWE-416

Follow this CVE

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.2%

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

Vendor	Product	CPE
qualcomm	msm8909w firmware	cpe:2.3:o:qualcomm:msm8909w_firmware
qualcomm	msm8909w	cpe:2.3:h:qualcomm:msm8909w
qualcomm	qcs405 firmware	cpe:2.3:o:qualcomm:qcs405_firmware
qualcomm	qcs405	cpe:2.3:h:qualcomm:qcs405
qualcomm	qcs605 firmware	cpe:2.3:o:qualcomm:qcs605_firmware
qualcomm	qcs605	cpe:2.3:h:qualcomm:qcs605
qualcomm	sd 425 firmware	cpe:2.3:o:qualcomm:sd_425_firmware
qualcomm	sd 425	cpe:2.3:h:qualcomm:sd_425
qualcomm	sd 427 firmware	cpe:2.3:o:qualcomm:sd_427_firmware
qualcomm	sd 427	cpe:2.3:h:qualcomm:sd_427
qualcomm	sd 430 firmware	cpe:2.3:o:qualcomm:sd_430_firmware
qualcomm	sd 430	cpe:2.3:h:qualcomm:sd_430

and 30 more

Affected versions

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

qualcomm msm8909w firmwareall versions
qualcomm qcs405 firmwareall versions
qualcomm qcs605 firmwareall versions
qualcomm sd 425 firmwareall versions
qualcomm sd 427 firmwareall versions
qualcomm sd 430 firmwareall versions
qualcomm sd 435 firmwareall versions
qualcomm sd 450 firmwareall versions
qualcomm sd 625 firmwareall versions
qualcomm sd 636 firmwareall versions
qualcomm sd 670 firmwareall versions
qualcomm sd 675 firmwareall versions
qualcomm sd 710 firmwareall versions
qualcomm sd 712 firmwareall versions
qualcomm sd 730 firmwareall versions
qualcomm sd 845 firmwareall versions
qualcomm sd 850 firmwareall versions
qualcomm sd 855 firmwareall versions
qualcomm sdm630 firmwareall versions
qualcomm sdm660 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 Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables
- MSM8909W, QCS405, QCS605, SD 425, SD 427, SD 430, SD 435, SD 450, SD 625, SD 636, SD 675, SD 712 / SD 710 / SD 670, SD 730, SD 845 / SD 850, SD 855, SDM630, SDM660, SDX24affected

Same product

qualcomm: all records

Other highest-scoring records for the same primary product.

CVE-2017-11076Use of Out-of-range Pointer Offset in Video
39Monitor
CVE-2019-2285Out of bound write issue is observed while giving information about properties that have been set so far for playing video in Snapdragon Aut
39Monitor
CVE-2019-10538Lack of check of address range received from firmware response allows modem to respond arbitrary pages into its address range which can comp
39Monitor
CVE-2019-10509Device record of the pairing device used after free during ACL disconnection in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity
39Monitor
CVE-2019-2259Resource allocation error while playing the video whose dimensions are more than supported dimension in Snapdragon Auto, Snapdragon Compute,
39Monitor
CVE-2019-2255An unprivileged user can craft a bitstream such that the payload encoded in the bitstream gains code execution in Snapdragon Auto, Snapdrago
39Monitor

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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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.

No nightly-computed relations.

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.0/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

www.codeaurora.org/security-bulletin/2019/07/01/july-2019-code-aurora-security-bulletin

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

All records

Noroxi analysis

No Noroxi analysis for this record yet

We use this product, ask for help

Data sources and verification

CNA: qualcomm

CVE.org (CNA)Aug 4, 2024, 6:42 PM UTC
NVDJun 16, 2026, 10:33 PM UTC
FIRST EPSSSep 29, 2026, 12:00 AM UTC

Each line is when that source was last processed for this record.

You’re seeing every CVE. Add your stack to narrow the list down to the ones that affect you.

Add your stack