CVE-2020-36791
net_sched: keep alloc_hash updated after hash allocation
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.4.218, 4.9.218, 4.14.175, 4.19.114, 5.4.29, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
From 4.4.214 · fixed in 4.4.218; From 4.9.214 · fixed in 4.9.218; From 4.14.171 · fixed in 4.14.175; From 4.19.103 · fixed in 4.19.114; From 5.4.19 · fixed in 5.4.29; From 5.5.3 · fixed in 5.5.14
References 9
git.kernel.org
- stable/c/d6cdc5bb19b595486fb2e6661e5138d73a57f454
- stable/c/c4453d2833671e3a9f6bd52f0f581056c3736386
- stable/c/9f8b6c44be178c2498a00b270872a6e30e7c8266
- stable/c/557d015ffb27b672e24e6ad141fd887783871dc2
- stable/c/d23faf32e577922b6da20bf3740625c1105381bf
- stable/c/bd3ee8fb6371b45c71c9345cc359b94da2ddefa9
- stable/c/0d1c3530e1bd38382edef72591b78e877e0edcd3