Possible use after free when process shell memory is freed using IOCTL munmap call and process initialization is in progress in Snapdragon A
Noroxi assessment
Priority: This week (action score 61/100)
- CISA has confirmed exploitation in the wild (Dec 5, 2023). Remediation deadline for US federal agencies: Dec 26, 2023.
- Probability of exploitation in the next 30 days: 0.41% (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.
Don’t wait for the next maintenance window. Until a fix is released, restrict access to the affected component and 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 · CISA KEV · FIRST EPSS
Possible use after free when process shell memory is freed using IOCTL munmap call and process initialization is in progress in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music
- Published
- Jun 14, 2022
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 33th percentile
- CWE
- CWE-416
Report tools
Action score
61
This week
Don’t wait for the next maintenance window.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 30 / 30 · Listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- active
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · qualcomm
- 8.4
- 0.6 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.
Actively exploited in the wild
CISA added this to its Known Exploited Vulnerabilities catalog on Dec 5, 2023. That signals real attacks, not theory.
Remediation deadline for US federal agencies: Dec 26, 2023.
Get told when this record changes
- In CISA KEV: exploitation in the wild confirmed
- Weaponized exploit exists
- 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
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 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 | apq8053 firmware | cpe:2.3:o:qualcomm:apq8053_firmware |
| qualcomm | apq8053 | cpe:2.3:h:qualcomm:apq8053 |
| qualcomm | ar8031 firmware | cpe:2.3:o:qualcomm:ar8031_firmware |
| qualcomm | ar8031 | cpe:2.3:h:qualcomm:ar8031 |
| qualcomm | ar8035 firmware | cpe:2.3:o:qualcomm:ar8035_firmware |
| qualcomm | ar8035 | cpe:2.3:h:qualcomm:ar8035 |
| qualcomm | csra6620 firmware | cpe:2.3:o:qualcomm:csra6620_firmware |
| qualcomm | csra6620 | cpe:2.3:h:qualcomm:csra6620 |
| qualcomm | csra6640 firmware | cpe:2.3:o:qualcomm:csra6640_firmware |
| qualcomm | csra6640 | cpe:2.3:h:qualcomm:csra6640 |
| qualcomm | mdm9150 firmware | cpe:2.3:o:qualcomm:mdm9150_firmware |
| qualcomm | mdm9150 | cpe:2.3:h:qualcomm:mdm9150 |
and 168 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm apq8053 firmwareall versions
- qualcomm ar8031 firmwareall versions
- qualcomm ar8035 firmwareall versions
- qualcomm csra6620 firmwareall versions
- qualcomm csra6640 firmwareall versions
- qualcomm mdm9150 firmwareall versions
- qualcomm msm8953 firmwareall versions
- qualcomm qca6174a firmwareall versions
- qualcomm qca6390 firmwareall versions
- qualcomm qca6391 firmwareall versions
- qualcomm qca6426 firmwareall versions
- qualcomm qca6436 firmwareall versions
- qualcomm qca6574 firmwareall versions
- qualcomm qca6574a firmwareall versions
- qualcomm qca6574au firmwareall versions
- qualcomm qca6595au firmwareall versions
- qualcomm qca6696 firmwareall versions
- qualcomm qca8081 firmwareall versions
- qualcomm qca8337 firmwareall versions
- qualcomm qca9377 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 Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music
- APQ8053, AR8031, AR8035, CSRA6620, CSRA6640, MDM9150, MSM8953, QCA6174A, QCA6390, QCA6391, QCA6426, QCA6436, QCA6574, QCA6574A, QCA6574AU, QCA6595AU, QCA6696, QCA8081, QCA8337, QCA9377, QCM2290, QCM42affected
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-11264Improper authentication of Non-EAPOL/WAPI plaintext frames during four-way handshake can lead to arbitrary network packet injection in Snapd43Plan
- CVE-2020-11153u'Out of bound memory access while processing GATT data received due to lack of check of pdu data length and leads to remote code execution'40Plan
- CVE-2020-3703u'Buffer over-read issue in Bluetooth peripheral firmware due to lack of check for invalid opcode and length of opcode received from central39Monitor
- CVE-2020-3628Improper access due to socket opened by the logging application without specifying localhost address in Snapdragon Consumer IOT, Snapdragon 39Monitor
- CVE-2019-14080Out of bound write can happen due to lack of check of array index value while parsing SDP attribute for SAR in Snapdragon Auto, Snapdragon C39Monitor
- CVE-2019-14131Out of bound write can occur in radio measurement request if STA receives multiple invalid rrm measurement request from AP in Snapdragon Aut39Monitor
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
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
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.
- Published
- CISA KEV+539 d
- TodayOct 16, 2026+1585 d
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
- 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 FreeCVSS 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 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);Fixed
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&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
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.