net/sched: act_skbedit: fix divide-by-zero in tcf_skbedit_hash()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 38a6f0865796e26fc38fff4858f681d9ae76fa0f · < be054cc66f739a9ba615dba9012a07fab8e7dd6f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net/sched: act_skbedit: fix divide-by-zero in tcf_skbedit_hash()
Commit 38a6f0865796 ("net: sched: support hash selecting tx queue") added SKBEDIT_F_TXQ_SKBHASH support. The inclusive range size is computed as:
mapping_mod = queue_mapping_max - queue_mapping + 1;
The range size can be 65536 when the requested range covers all possible u16 queue IDs (e.g. queue_mapping=0 and queue_mapping_max=U16_MAX). That value cannot be represented in a u16 and previously wrapped to 0, so tcf_skbedit_hash() could trigger a divide-by-zero:
queue_mapping += skb_get_hash(skb) % params->mapping_mod;
Compute mapping_mod in a wider type and reject ranges larger than U16_MAX to prevent params->mapping_mod from becoming 0 and avoid the crash.
From the CVE record · Linux
The Linux kernel’s skbedit transmit-queue hash action could divide by zero when configured with a queue range covering all possible u16 queue IDs. Triggering that condition could crash the kernel. The input does not specify whether an attacker needs local or network access, authentication, or user interaction.
Teams running the Linux kernel should check whether their kernel includes the affected skbedit code; affected versions are not specified.