net_sched: keep alloc_hash updated after hash allocation
3Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackepss 0.2%
exploitation probability
0.2%top 94% of all CVEs
observed exploitation
nono source reports it
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 products
Linux · LinuxReferences
https://blog.cdthoughts.ch/2021/03/16/syzbot-bug.htmlhttps://git.kernel.org/stable/c/0d1c3530e1bd38382edef72591b78e877e0edcd3https://git.kernel.org/stable/c/557d015ffb27b672e24e6ad141fd887783871dc2https://git.kernel.org/stable/c/9f8b6c44be178c2498a00b270872a6e30e7c8266https://git.kernel.org/stable/c/bd3ee8fb6371b45c71c9345cc359b94da2ddefa9https://git.kernel.org/stable/c/c4453d2833671e3a9f6bd52f0f581056c3736386https://git.kernel.org/stable/c/d23faf32e577922b6da20bf3740625c1105381bfhttps://git.kernel.org/stable/c/d6cdc5bb19b595486fb2e6661e5138d73a57f454https://syzkaller.appspot.com/bug?id=ea260693da894e7b078d18fca2c9c0a19b457534