Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-02-28. NVD baseline CVSS 7.8; sources differ by 0.0.
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
In the Linux kernel, the following vulnerability has been resolved:
media: atomisp: Fix use after free in atomisp_alloc_css_stat_bufs()
The "s3a_buf" is freed along with all the other items on the "asd->s3a_stats" list. It leads to a double free and a use after free.
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
February 28, 2024
August 26, 2026
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| linux | — | 5.10.38-1 | — |
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| linux | — | 5.10.38-1 | — |
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| linux | — | 5.10.38-1 | — |
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| linux | — | 5.10.38-1 | — |
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 156 total refreshes for this CVE.
See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-36785
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.