SUSE CVE-2020-36791

In the Linux kernel, the following vulnerability has been resolved: netsched: keep allochash updated after hash allocation In commit 599be01ee567 "netsched: fix an OOB access in clstcindex" I moved cp-hash calculation before the first tcindexallocperfecthash, but cp-allochash is left untouched...

CVE-2020-36791

In the Linux kernel, the following vulnerability has been resolved: netsched: keep allochash updated after hash allocation In commit 599be01ee567 "netsched: fix an OOB access in clstcindex" I moved cp-hash calculation before the first tcindexallocperfecthash, but cp-allochash is left untouched...

CVE-2020-36791

In the Linux kernel, the following vulnerability has been resolved: netsched: keep allochash updated after hash allocation In commit 599be01ee567 "netsched: fix an OOB access in clstcindex" I moved cp-hash calculation before the first tcindexallocperfecthash, but cp-allochash is left untouched...

UBUNTU-CVE-2020-36791

In the Linux kernel, the following vulnerability has been resolved: netsched: keep allochash updated after hash allocation In commit 599be01ee567 "netsched: fix an OOB access in clstcindex" I moved cp-hash calculation before the first tcindexallocperfecthash, but cp-allochash is left untouched...

CVE-2020-36791

The CVE-2020-36791 entry refers to a Linux kernel net_sched issue where cp->alloc_hash could be left at an incorrect size after a hash allocation, enabling a potential out-of-bounds access. The described root cause is that the hash calculation was moved before tcindex_alloc_perfect_hash() but ...

PT-2025-20071 · Linux · Linux Kernel

Name of the Vulnerable Software and Affected Versions: Linux kernel affected versions not specified Description: A vulnerability in the Linux kernel has been resolved, related to the net sched component. The issue arises from the cp-alloc hash not being updated after hash allocation in tcindex...