CVE-2020-36791
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…
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.19%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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().
- CVSS 3.1
- 7.1 HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
- EPSS
- 0.19% probability · 9th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-125
- Affected
- linux/linux kernel
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
References
- https://blog.cdthoughts.ch/2021/03/16/syzbot-bug.htmlThird Party Advisory
- https://git.kernel.org/stable/c/0d1c3530e1bd38382edef72591b78e877e0edcd3Patch
- https://git.kernel.org/stable/c/557d015ffb27b672e24e6ad141fd887783871dc2Patch
- https://git.kernel.org/stable/c/9f8b6c44be178c2498a00b270872a6e30e7c8266Patch
- https://git.kernel.org/stable/c/bd3ee8fb6371b45c71c9345cc359b94da2ddefa9Patch
- https://git.kernel.org/stable/c/c4453d2833671e3a9f6bd52f0f581056c3736386Patch
- https://git.kernel.org/stable/c/d23faf32e577922b6da20bf3740625c1105381bfPatch
- https://git.kernel.org/stable/c/d6cdc5bb19b595486fb2e6661e5138d73a57f454Patch
- https://syzkaller.appspot.com/bug?id=ea260693da894e7b078d18fca2c9c0a19b457534Issue Tracking
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.