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().
Metrics
Affected Vendors & Products
References
History
Mon, 14 Jul 2025 13:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
epss
|
epss
|
Thu, 08 May 2025 13:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|
Wed, 07 May 2025 14:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
|
Wed, 07 May 2025 13:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
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(). | |
Title | net_sched: keep alloc_hash updated after hash allocation | |
References |
|
|

Status: PUBLISHED
Assigner: Linux
Published: 2025-05-07T13:17:33.882Z
Updated: 2025-05-07T14:12:46.187Z
Reserved: 2024-02-26T17:07:27.435Z
Link: CVE-2020-36791

No data.

Status : Awaiting Analysis
Published: 2025-05-07T14:15:28.513
Modified: 2025-05-08T14:39:18.800
Link: CVE-2020-36791
