net_sched: keep alloc_hash updated after hash allocation
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2c66ff8d08f81bcf8e8cb22e31e39c051b15336a · < bd3ee8fb6371b45c71c9345cc359b94da2ddefa9| No fix yet |
| Linux Linux |
| No fix yet |
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().
From the CVE record · Linux
The Linux kernel's net_sched cls_tcindex code can access memory out of bounds because alloc_hash is not updated after a hash allocation. The input does not specify how an attacker could trigger the issue, whether authentication or user interaction is required, or its resulting impact.
Engineers running the Linux kernel should check their versions; affected versions are not specified in the input.