net: sched: fix memory leak in tcindex_partial_destroy_work
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 331b72922c5f58d48fd5500acadc91777cc31970 · < 18c3fa7a7fdbb4d21dafc8a7710ae2c1680930f6| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: sched: fix memory leak in tcindex_partial_destroy_work
Syzbot reported memory leak in tcindex_set_parms(). The problem was in non-freed perfect hash in tcindex_partial_destroy_work().
In tcindex_set_parms() new tcindex_data is allocated and some fields from old one are copied to new one, but not the perfect hash. Since tcindex_partial_destroy_work() is the destroy function for old tcindex_data, we need to free perfect hash to avoid memory leak.
From the CVE record · Linux
A perfect hash is not freed during tcindex cleanup in the Linux kernel, causing a memory leak. Repeated triggering could consume memory; the input does not specify how an attacker could trigger it or whether network access, authentication, or user interaction is required.
Engineers running the Linux kernel should check their versions; affected versions are not specified in the input.