CVEvulnerability
CVE-2020-36791
7.1 HIGH
Official page ↗
- Status
- Modified
- Published
- 2025-05-07
- Last modified
- 2026-08-04
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
- 7.8 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CVSS 3.1 ([email protected])
- 7.1 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
- Weaknesses
- CWE-125
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().
Affected configurations
• linux linux kernel (>= 4.4.214 < 4.4.218)
• linux linux kernel (>= 4.9.214 < 4.9.218)
• linux linux kernel (>= 4.14.171 < 4.14.175)
• linux linux kernel (>= 4.19.103 < 4.19.114)
• linux linux kernel (>= 5.4.19 < 5.4.29)
• linux linux kernel (>= 5.5.3 < 5.5.14)
• linux linux kernel 5.6
Related
Weakness · CWE (1)
- CWE-125 Out-of-bounds Read weakness
References
- https://blog.cdthoughts.ch/2021/03/16/syzbot-bug.html Third Party Advisory
- https://git.kernel.org/stable/c/0d1c3530e1bd38382edef72591b78e877e0edcd3 Patch
- https://git.kernel.org/stable/c/557d015ffb27b672e24e6ad141fd887783871dc2 Patch
- https://git.kernel.org/stable/c/9f8b6c44be178c2498a00b270872a6e30e7c8266 Patch
- https://git.kernel.org/stable/c/bd3ee8fb6371b45c71c9345cc359b94da2ddefa9 Patch
- https://git.kernel.org/stable/c/c4453d2833671e3a9f6bd52f0f581056c3736386 Patch
- https://git.kernel.org/stable/c/d23faf32e577922b6da20bf3740625c1105381bf Patch
- https://git.kernel.org/stable/c/d6cdc5bb19b595486fb2e6661e5138d73a57f454 Patch
- https://syzkaller.appspot.com/bug?id=ea260693da894e7b078d18fca2c9c0a19b457534 Issue Tracking