Answer in brief
CVE-2020-36791 records a High severity (CVSS 7.8) vulnerability in net_sched: keep alloc_hash updated after hash allocation. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2020-36791 records a High severity (CVSS 7.8) vulnerability in net_sched: keep alloc_hash updated after hash allocation. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.6:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.6:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.6:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.6:rc4:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.6:rc5:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.6:rc6:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.6:rc7:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=73c29d2f6f8ae731b1e09051b69ed3ba2319482b <d6cdc5bb19b595486fb2e6661e5138d73a57f454 || >=b974ac51f5834a729de252fc5c1c9de9efd79b45 <c4453d2833671e3a9f6bd52f0f581056c3736386 || >=6cb448ee493c8a514c9afa0c346f3f5b3227de85 <9f8b6c44be178c2498a00b270872a6e30e7c8266 || >=478c4b2ffd44e5186c7e22ae7c38a86a5b9cfde5 <557d015ffb27b672e24e6ad141fd887783871dc2 || >=dd8142a6fa5270783d415292ec8169f4ea2a5468 <d23faf32e577922b6da20bf3740625c1105381bf || >=2c66ff8d08f81bcf8e8cb22e31e39c051b15336a <bd3ee8fb6371b45c71c9345cc359b94da2ddefa9 || >=599be01ee567b61f4471ee8078870847d0a11e8e <0d1c3530e1bd38382edef72591b78e877e0edcd3 | d6cdc5bb19b595486fb2e6661e5138d73a57f454, c4453d2833671e3a9f6bd52f0f581056c3736386, 9f8b6c44be178c2498a00b270872a6e30e7c8266, 557d015ffb27b672e24e6ad141fd887783871dc2, d23faf32e577922b6da20bf3740625c1105381bf, bd3ee8fb6371b45c71c9345cc359b94da2ddefa9, 0d1c3530e1bd38382edef72591b78e877e0edcd3 |
| Linux/Linuxgeneric | >=4.4.214 <4.4.218 || >=4.9.214 <4.9.218 || >=4.14.171 <4.14.175 || >=4.19.103 <4.19.114 || >=5.4.19 <5.4.29 || >=5.5.3 <5.5.14 | 4.4.218, 4.9.218, 4.14.175, 4.19.114, 5.4.29, 5.5.14 |
Published upstream
May 7, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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().
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.6:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.6:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.6:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.6:rc4:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.6:rc5:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.6:rc6:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.6:rc7:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=73c29d2f6f8ae731b1e09051b69ed3ba2319482b <d6cdc5bb19b595486fb2e6661e5138d73a57f454 || >=b974ac51f5834a729de252fc5c1c9de9efd79b45 <c4453d2833671e3a9f6bd52f0f581056c3736386 || >=6cb448ee493c8a514c9afa0c346f3f5b3227de85 <9f8b6c44be178c2498a00b270872a6e30e7c8266 || >=478c4b2ffd44e5186c7e22ae7c38a86a5b9cfde5 <557d015ffb27b672e24e6ad141fd887783871dc2 || >=dd8142a6fa5270783d415292ec8169f4ea2a5468 <d23faf32e577922b6da20bf3740625c1105381bf || >=2c66ff8d08f81bcf8e8cb22e31e39c051b15336a <bd3ee8fb6371b45c71c9345cc359b94da2ddefa9 || >=599be01ee567b61f4471ee8078870847d0a11e8e <0d1c3530e1bd38382edef72591b78e877e0edcd3 | d6cdc5bb19b595486fb2e6661e5138d73a57f454, c4453d2833671e3a9f6bd52f0f581056c3736386, 9f8b6c44be178c2498a00b270872a6e30e7c8266, 557d015ffb27b672e24e6ad141fd887783871dc2, d23faf32e577922b6da20bf3740625c1105381bf, bd3ee8fb6371b45c71c9345cc359b94da2ddefa9, 0d1c3530e1bd38382edef72591b78e877e0edcd3 |
| Linux/Linuxgeneric | >=4.4.214 <4.4.218 || >=4.9.214 <4.9.218 || >=4.14.171 <4.14.175 || >=4.19.103 <4.19.114 || >=5.4.19 <5.4.29 || >=5.5.3 <5.5.14 | 4.4.218, 4.9.218, 4.14.175, 4.19.114, 5.4.29, 5.5.14 |
Published upstream
May 7, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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().
Quoted source text, attributed separately from HOL analysis.