CVE-2020-36791

net_sched: keep alloc_hash updated after hash allocation

HIGH

7.1

CVSS Score

Published: May 7, 2025 at 01:17 PM UTC

Updated: August 4, 2026 at 04:06 PM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.1

Exploit prediction

EPSS 0.2%

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().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

4.14.171 ≤ v < 4.14.1754.19.103 ≤ v < 4.19.1144.4.214 ≤ v < 4.4.2184.9.214 ≤ v < 4.9.2185.4.19 ≤ v < 5.4.295.5.3 ≤ v < 5.5.142c66ff8d08f81bcf8e8cb22e31e39c051b15336a4.14.171 4.19.103 4.4.214 4.9.214478c4b2ffd44e5186c7e22ae7c38a86a5b9cfde55.4.19 5.5.3 5.6 rc1 5.6 rc2 5.6 rc3 5.6 rc4 5.6 rc5 5.6 rc6 5.6 rc7599be01ee567b61f4471ee8078870847d0a11e8e6cb448ee493c8a514c9afa0c346f3f5b3227de8573c29d2f6f8ae731b1e09051b69ed3ba2319482bb974ac51f5834a729de252fc5c1c9de9efd79b45dd8142a6fa5270783d415292ec8169f4ea2a5468

Vendor states this is fixed in 0d1c3530e1bd38382edef72591b78e877e0edcd3 (fixed)

Vendor states this is fixed in 557d015ffb27b672e24e6ad141fd887783871dc2 (fixed)

Vendor states this is fixed in 9f8b6c44be178c2498a00b270872a6e30e7c8266 (fixed)

Vendor states this is fixed in bd3ee8fb6371b45c71c9345cc359b94da2ddefa9 (fixed)

Vendor states this is fixed in c4453d2833671e3a9f6bd52f0f581056c3736386 (fixed)

Vendor states this is fixed in d23faf32e577922b6da20bf3740625c1105381bf (fixed)

Vendor states this is fixed in d6cdc5bb19b595486fb2e6661e5138d73a57f454 (fixed)

Affected range stops below 4.14.175, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.19.114, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.4.218, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.9.218, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.4.29, so it looks safe — our inference, not a vendor statement