CVE-2020-36791net_sched: keep alloc_hash updated after hash allocation
- 7.8HighCVSS base score
- 0.20%Exploitation in 30 daysEPSS · top 90% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: net_sched: keep alloc_hash updated after hash allocation In commit 599be01ee567 ("net_sched: fix an OOB access in cls_tcindex") I moved cp->hash calculation before the first tcindex_alloc_perfect_hash(), but cp->alloc_hash is left untouched. This difference could lead to another out of bound access. cp->alloc_hash should always be the size allocated, we should update it after this tcindex_alloc_perfect_hash().
Timeline
ID reserved
By Linux
- 15 months later
· 15 months later
Published
- 15 months later
· 15 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.20% · top 90% of all CVEs (18 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 73c29d2f6f8ae731b1e09051b69ed3ba2319482b – < d6cdc5bb19b595486fb2e6661e5138d73a57f454
- affected b974ac51f5834a729de252fc5c1c9de9efd79b45 – < c4453d2833671e3a9f6bd52f0f581056c3736386
- affected 6cb448ee493c8a514c9afa0c346f3f5b3227de85 – < 9f8b6c44be178c2498a00b270872a6e30e7c8266
- affected 478c4b2ffd44e5186c7e22ae7c38a86a5b9cfde5 – < 557d015ffb27b672e24e6ad141fd887783871dc2
- affected dd8142a6fa5270783d415292ec8169f4ea2a5468 – < d23faf32e577922b6da20bf3740625c1105381bf
- affected 2c66ff8d08f81bcf8e8cb22e31e39c051b15336a – < bd3ee8fb6371b45c71c9345cc359b94da2ddefa9
- affected 599be01ee567b61f4471ee8078870847d0a11e8e – < 0d1c3530e1bd38382edef72591b78e877e0edcd3
- affected 4.4.214 – < 4.4.218
- affected 4.9.214 – < 4.9.218
- affected 4.14.171 – < 4.14.175
- affected 4.19.103 – < 4.19.114
- affected 5.4.19 – < 5.4.29
- affected 5.5.3 – < 5.5.14
References
References9
- https://git.kernel.org/stable/c/d6cdc5bb19b595486fb2e6661e5138d73a57f454 (opens in a new tab)
- https://git.kernel.org/stable/c/c4453d2833671e3a9f6bd52f0f581056c3736386 (opens in a new tab)
- https://git.kernel.org/stable/c/9f8b6c44be178c2498a00b270872a6e30e7c8266 (opens in a new tab)
- https://git.kernel.org/stable/c/557d015ffb27b672e24e6ad141fd887783871dc2 (opens in a new tab)
- https://git.kernel.org/stable/c/d23faf32e577922b6da20bf3740625c1105381bf (opens in a new tab)
- https://git.kernel.org/stable/c/bd3ee8fb6371b45c71c9345cc359b94da2ddefa9 (opens in a new tab)
- https://git.kernel.org/stable/c/0d1c3530e1bd38382edef72591b78e877e0edcd3 (opens in a new tab)
- https://syzkaller.appspot.com/bug?id=ea260693da894e7b078d18fca2c9c0a19b457534 (opens in a new tab)
- https://blog.cdthoughts.ch/2021/03/16/syzbot-bug.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2020-24232 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2020-36791)Record last updated .