net/sched: fq_pie: clamp default quantum to avoid signed overflow
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ec97ecf1ebe485a17cd8395a5f35e6b80b57665a · < 044fa2498bbc2900f0c48a6ef2fdd5b2bdfc3795| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net/sched: fq_pie: clamp default quantum to avoid signed overflow
fq_pie_init() sets q->quantum = psched_mtu(qdisc_dev(sch)) without clamping. A device with a huge MTU (e.g. dummy with max_mtu == 0 accepting MTU 2147483634) makes psched_mtu() return 0x80000000, which overflows the signed flow->deficit to INT_MIN in fq_pie_qdisc_dequeue(), causing an infinite loop and soft lockup. Emulate fq_pie_policy which is already bounded to [1, 1 << 20]; clamp the default to [256, 1 << 20]. 256 matches fq_codel's floor and is a sane minimum for a DRR quantum.
Conditions to recreate the bug: a device whose MTU (plus hard_header_len) wraps psched_mtu() into the sign bit (e.g. a dummy device with max_mtu == 0 accepting MTU 2147483634). Requires CAP_NET_ADMIN in a user namespace.
From the CVE record · Linux
The Linux kernel's fq_pie scheduler can enter an infinite loop and cause a soft lockup when a device has an unusually large MTU. Triggering this requires CAP_NET_ADMIN in a user namespace and an MTU that makes psched_mtu() set the sign bit; no user interaction is described.
Engineers running Linux kernels with the fq_pie scheduler should check their kernel version against the vendor advisory; affected versions were not provided.