Memory corruption due to invalid value of total dimension in the non-histogram type KPI could lead to a denial of service in Snapdragon Auto
Memory corruption due to invalid value of total dimension in the non-histogram type KPI could lead to a denial of service in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Mobile
- Published
- Apr 7, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.4% · 36th percentile
- CWE
- CWE-787
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CNA vs NVD score
- NVD
- 5.5
- CNA · qualcomm
- 8.4
- 2.9 point gap
CVSS:3.1/AV:L/AC:L/PR:N/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.
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 helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| qualcomm | csrb31024 firmware | cpe:2.3:o:qualcomm:csrb31024_firmware |
| qualcomm | csrb31024 | cpe:2.3:h:qualcomm:csrb31024 |
| qualcomm | pm3003a firmware | cpe:2.3:o:qualcomm:pm3003a_firmware |
| qualcomm | pm3003a | cpe:2.3:h:qualcomm:pm3003a |
| qualcomm | pm6150a firmware | cpe:2.3:o:qualcomm:pm6150a_firmware |
| qualcomm | pm6150a | cpe:2.3:h:qualcomm:pm6150a |
| qualcomm | pm6150l firmware | cpe:2.3:o:qualcomm:pm6150l_firmware |
| qualcomm | pm6150l | cpe:2.3:h:qualcomm:pm6150l |
| qualcomm | pm6350 firmware | cpe:2.3:o:qualcomm:pm6350_firmware |
| qualcomm | pm6350 | cpe:2.3:h:qualcomm:pm6350 |
| qualcomm | pm7150a firmware | cpe:2.3:o:qualcomm:pm7150a_firmware |
| qualcomm | pm7150a | cpe:2.3:h:qualcomm:pm7150a |
and 188 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm csrb31024 firmwareall versions
- qualcomm pm3003a firmwareall versions
- qualcomm pm6150a firmwareall versions
- qualcomm pm6150l firmwareall versions
- qualcomm pm6350 firmwareall versions
- qualcomm pm7150a firmwareall versions
- qualcomm pm7150l firmwareall versions
- qualcomm pm7250 firmwareall versions
- qualcomm pm7250b firmwareall versions
- qualcomm pm8008 firmwareall versions
- qualcomm pm8009 firmwareall versions
- qualcomm pm8150a firmwareall versions
- qualcomm pm8150b firmwareall versions
- qualcomm pm8150c firmwareall versions
- qualcomm pm8150l firmwareall versions
- qualcomm pm8250 firmwareall versions
- qualcomm pm8350 firmwareall versions
- qualcomm pm8350b firmwareall versions
- qualcomm pm8350bh firmwareall versions
- qualcomm pm8350c 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 Connectivity, Snapdragon Mobile
- CSRB31024, PM3003A, PM6150A, PM6150L, PM6350, PM7150A, PM7150L, PM7250, PM7250B, PM8008, PM8009, PM8150A, PM8150B, PM8150C, PM8150L, PM8250, PM8350, PM8350B, PM8350BH, PM8350C, PM855, PM855B, PM855L, affected
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-28572Buffer Over-read in WLAN HOST35Monitor
- CVE-2024-43066Use After Free in HLOS31Monitor
- CVE-2020-11237Memory crash when accessing histogram type KPI input received due to lack of check of histogram definition before accessing it in Snapdragon31Monitor
- CVE-2020-11273Histogram type KPI was teardown with the assumption of the existence of histogram binning info and will lead to null pointer access when his30Monitor
- CVE-2020-11186Modem will enter into busy mode in an infinite loop while parsing histogram dimension due to improper validation of input received in Snapdr22Monitor
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.
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 researchersFinders, 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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
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
Vendor advisories and official records. Exploit/PoC links are deliberately left out.