CVE-2026-90074

net/sched: fq_pie: clamp default quantum to avoid signed overflow

N/A
Published: September 17, 2026 at 04:05 PM UTC
Updated: October 19, 2026 at 09:18 AM 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
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

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

5.6ec97ecf1ebe485a17cd8395a5f35e6b80b57665a
Vendor states this is fixed in 044fa2498bbc2900f0c48a6ef2fdd5b2bdfc3795 (fixed)
Vendor states this is fixed in 1f43e4dbc93b7d02761a024d5f895df823c07b72 (fixed)
Vendor states this is fixed in 435da3734a8e63d3067016accc977ed1d10aaaa0 (fixed)
Vendor states this is fixed in 44dad8fe99b58a7fe2961e9eec6a5f07ace5b51f (fixed)
Vendor states this is fixed in 6f1be05faecef4c0f9a008200209f66ef2e133f7 (fixed)
Vendor states this is fixed in bf97fd2163ad1191ef8daa3d4df8372aee19e396 (fixed)
Vendor states this is fixed in c86cd7ed0b0e44779a3d1683f03e4353baf4bdc9 (fixed)
Vendor states this is fixed in f7942b2693bc24c7d609a03d06f97bee3b0bd96a (fixed)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 5.6 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card