CVE-2019-2345: Race condition while accessing DMA buffer in jpeg driver in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon…
Noroxi assessment
Priority: Monitor (action score 28/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.13% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- 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
Race condition while accessing DMA buffer in jpeg driver in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables in MSM8909W, MSM8996AU, QCS605, SD 425, SD 427, SD 430, SD 435, SD 450, SD 625, SD 636, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SDA660, SDM660, SDX20, SDX24
- Published
- Jul 25, 2019
- Updated
- Jun 16, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-362
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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 itNoroxi 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 helpAffected 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 | msm8909w firmware | cpe:2.3:o:qualcomm:msm8909w_firmware |
| qualcomm | msm8909w | cpe:2.3:h:qualcomm:msm8909w |
| qualcomm | msm8996au firmware | cpe:2.3:o:qualcomm:msm8996au_firmware |
| qualcomm | msm8996au | cpe:2.3:h:qualcomm:msm8996au |
| 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 32 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 Auto, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables
- MSM8909W, MSM8996AU, QCS605, SD 425, SD 427, SD 430, SD 435, SD 450, SD 625, SD 636, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SDA660, SDM660, SDX20, SDX24affected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm msm8909w firmwareall versions
- qualcomm msm8996au 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 710 firmwareall versions
- qualcomm sd 712 firmwareall versions
- qualcomm sd 820 firmwareall versions
- qualcomm sd 820a firmwareall versions
- qualcomm sd 835 firmwareall versions
- qualcomm sd 845 firmwareall versions
- qualcomm sd 850 firmwareall versions
- qualcomm sda660 firmwareall versions
- qualcomm sdm660 firmwareall versions
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-11076Use of Out-of-range Pointer Offset in Video39Monitor
- 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…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…39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2019-2314Jul 25, 2019 · Possible race condition that will cause a use-after-free when writing to two sysfs entries at nearly the same time in Snapdragon Compute…28Monitor
- ← EarlierCVE-2019-2343Jul 25, 2019 · Out of bound read and information disclosure in firmware due to insufficient checking of an embedded structure that can be sent from a…22Monitor
- Later →CVE-2019-10509Sep 30, 2019 · Device record of the pairing device used after free during ACL disconnection in Snapdragon Auto, Snapdragon Compute, Snapdragon…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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · 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.
- Special conditions such as timing or configuration are required.
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
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.