NVD / CVE Program· CNA qualcomm

CVE-2019-10548: While trying to obtain datad ipc handle during DPL initialization, Heap use-after-free issue can occur if modem SSR occurs at same time in S

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.20% (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

While trying to obtain datad ipc handle during DPL initialization, Heap use-after-free issue can occur if modem SSR occurs at same time in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Wearables in APQ8009, APQ8053, APQ8096AU, MSM8905, MSM8909, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8939, MSM8940, MSM8953, MSM8996AU, MSM8998, Nicobar, QCA6574AU, QCS605, QM215, SDA660, SDM429, SDM429W, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SM6150, SM7150, SM8150, SXR1130

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

Memory safety

Published: Jan 21, 2020
Updated: Jun 16, 2026
EPSS: 0.2% · 10th 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.2%

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	apq8009 firmware	cpe:2.3:o:qualcomm:apq8009_firmware
qualcomm	apq8009	cpe:2.3:h:qualcomm:apq8009
qualcomm	apq8053 firmware	cpe:2.3:o:qualcomm:apq8053_firmware
qualcomm	apq8053	cpe:2.3:h:qualcomm:apq8053
qualcomm	apq8096au firmware	cpe:2.3:o:qualcomm:apq8096au_firmware
qualcomm	apq8096au	cpe:2.3:h:qualcomm:apq8096au
qualcomm	msm8905 firmware	cpe:2.3:o:qualcomm:msm8905_firmware
qualcomm	msm8905	cpe:2.3:h:qualcomm:msm8905
qualcomm	msm8909 firmware	cpe:2.3:o:qualcomm:msm8909_firmware
qualcomm	msm8909	cpe:2.3:h:qualcomm:msm8909
qualcomm	msm8909w firmware	cpe:2.3:o:qualcomm:msm8909w_firmware
qualcomm	msm8909w	cpe:2.3:h:qualcomm:msm8909w

and 56 more

Affected versions

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

qualcomm apq8009 firmwareall versions
qualcomm apq8053 firmwareall versions
qualcomm apq8096au firmwareall versions
qualcomm msm8905 firmwareall versions
qualcomm msm8909 firmwareall versions
qualcomm msm8909w firmwareall versions
qualcomm msm8917 firmwareall versions
qualcomm msm8920 firmwareall versions
qualcomm msm8937 firmwareall versions
qualcomm msm8939 firmwareall versions
qualcomm msm8940 firmwareall versions
qualcomm msm8953 firmwareall versions
qualcomm msm8996au firmwareall versions
qualcomm msm8998 firmwareall versions
qualcomm nicobar firmwareall versions
qualcomm qca6574au firmwareall versions
qualcomm qcs605 firmwareall versions
qualcomm qm215 firmwareall versions
qualcomm sda660 firmwareall versions
qualcomm sdm429 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 Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Wearables
- APQ8009, APQ8053, APQ8096AU, MSM8905, MSM8909, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8939, MSM8940, MSM8953, MSM8996AU, MSM8998, Nicobar, QCA6574AU, QCS605, QM215, SDA660, SDM429, SDM429W, SDM439, Saffected

Same product

qualcomm: all records

Other highest-scoring records for the same primary product.

CVE-2020-11261Memory corruption due to improper check to return error when user application requests memory allocation of a huge size in Snapdragon Auto, KEV
61This week
CVE-2021-1905Possible use after free due to improper handling of memory mapping of multiple processes simultaneously.KEV
61This week
CVE-2021-1906Improper handling of address deregistration on failure can lead to new GPU address allocation failure.KEV
52Plan

Published before and after this one in the same product

← EarlierCVE-2019-2242Dec 18, 2019 · Device memory may get corrupted because of buffer overflow/underflow.
39Monitor
← EarlierCVE-2019-10532Jan 21, 2020 · Null-pointer dereference issue can occur while calculating string length when source string length is zero in Snapdragon Auto, Snapdragon Co
39Monitor
Later →CVE-2019-10558Jan 21, 2020 · While transferring data from APPS to DSP, Out of bound in FastRPC HLOS Driver due to the data buffer which can be controlled by DSP in Snapd
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.

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

www.qualcomm.com/company/product-security/bulletins/january-2020-bulletin

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

All records