Transient DOS due to loop with unreachable exit condition in WLAN firmware while parsing IPV6 extension header.
Noroxi assessment
Priority: Monitor (action score 30/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.42% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- 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
Transient DOS due to loop with unreachable exit condition in WLAN firmware while parsing IPV6 extension header. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking
- Published
- Nov 15, 2022
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 35th percentile
- CWE
- CWE-835
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · qualcomm
- 7.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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
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 | apq8009 firmware | cpe:2.3:o:qualcomm:apq8009_firmware |
| qualcomm | apq8009 | cpe:2.3:h:qualcomm:apq8009 |
| qualcomm | apq8017 firmware | cpe:2.3:o:qualcomm:apq8017_firmware |
| qualcomm | apq8017 | cpe:2.3:h:qualcomm:apq8017 |
| qualcomm | apq8096au firmware | cpe:2.3:o:qualcomm:apq8096au_firmware |
| qualcomm | apq8096au | cpe:2.3:h:qualcomm:apq8096au |
| qualcomm | aqt1000 firmware | cpe:2.3:o:qualcomm:aqt1000_firmware |
| qualcomm | aqt1000 | cpe:2.3:h:qualcomm:aqt1000 |
| 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 |
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 apq8009 firmwareall versions
- qualcomm apq8017 firmwareall versions
- qualcomm apq8096au firmwareall versions
- qualcomm aqt1000 firmwareall versions
- qualcomm ar8031 firmwareall versions
- qualcomm ar8035 firmwareall versions
- qualcomm csr8811 firmwareall versions
- qualcomm csra6620 firmwareall versions
- qualcomm csra6640 firmwareall versions
- qualcomm csrb31024 firmwareall versions
- qualcomm ipq5010 firmwareall versions
- qualcomm ipq5018 firmwareall versions
- qualcomm ipq5028 firmwareall versions
- qualcomm ipq6000 firmwareall versions
- qualcomm ipq6010 firmwareall versions
- qualcomm ipq6018 firmwareall versions
- qualcomm ipq6028 firmwareall versions
- qualcomm ipq8070 firmwareall versions
- qualcomm ipq8070a firmwareall versions
- qualcomm ipq8071a 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 Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Mu
- APQ8009, APQ8017, APQ8096AU, AQT1000, AR8031, AR8035, CSR8811, CSRA6620, CSRA6640, CSRB31024, IPQ5010, IPQ5018 … (+28)affected
Same product
qualcomm: all recordsOther 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, KEV61This week
- CVE-2021-1905Possible use after free due to improper handling of memory mapping of multiple processes simultaneously.KEV61This week
- CVE-2021-1906Improper handling of address deregistration on failure can lead to new GPU address allocation failure.KEV52Plan
Published before and after this one in the same product
- ← EarlierCVE-2022-25724Nov 15, 2022 · Memory corruption in graphics due to buffer overflow while validating the user address in Snapdragon Auto, Snapdragon Compute, Snapdragon Co31Monitor
- ← EarlierCVE-2022-25743Nov 15, 2022 · Memory corruption in graphics due to use-after-free while importing graphics buffer in Snapdragon Auto, Snapdragon Compute, Snapdragon Conne31Monitor
- Later →CVE-2022-25682Dec 13, 2022 · Memory corruption in MODEM UIM due to usage of out of range pointer offset while decoding command from card in Snapdragon Auto, Snapdragon C31Monitor
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
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- 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
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/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.