CVE-2020-11179
Description revised (poc_count, poc_public, poc_url). The record changed; nothing in the observed threat did.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- No fix version is held. The CNA's first reference is the place to look: qualcomm.com
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
Arbitrary read and write to kernel addresses by temporarily overwriting ring buffer pointer and creating a race condition. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables
- weakness
- Arbitrary Read and Write Access in Kernel
- affected
- Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables
- versions
- No affected-version range in held sources.
- fixed in
- No fix version in held sources.
- assigned by
- qualcomm
- published
- 2021-01-21
check us qualcomm.com
Exploit code held, dated
- exploit code
- 1 public proof-of-concept repository, first seen 2024-10-28 (PoC-in-GitHub).
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 14 Apr 2021 | 0.00416 | |
| 6 Jan 2022 | 0.0184 | |
| 4 Feb 2022 | 0.01404 | |
| 1 Apr 2022 | 0.00885 | |
| 7 Mar 2023 | 0.00044 | scoring model v2023.03.01 |
| 17 Mar 2025 | 0.02251 | scoring model v2025.03.14 |
| 15 Sep 2025 | 0.02099 | |
| 18 Nov 2025 | 0.00949 | |
| 21 Nov 2025 | 0.02099 | |
| 15 Jun 2026 | 0.00316 | scoring model v2026.06.15 |
17 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.00 on 2026-06-15 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- No fix version is held. One published by the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2020-11179', '2026-10-29T23:59:59.999999Z', now());