Linux Kernel up to 7.2.5 fq_pie net/sched/fq_pie.c fq_pie_init quantum/deficit infinite loop

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.0 | $0-$5k | 0.41+ |
Summary
A vulnerability, which was classified as problematic, was found in Linux Kernel up to 7.2.5. This affects the function fq_pie_init of the file net/sched/fq_pie.c of the component fq_pie. Such manipulation of the argument quantum/deficit leads to infinite loop.
This vulnerability is uniquely identified as CVE-2026-90074. Local access is required to approach this attack. No exploit exists.
You should upgrade the affected component.
Details
A vulnerability was found in Linux Kernel up to 7.2.5 and classified as problematic. Affected by this issue is the function fq_pie_init of the file net/sched/fq_pie.c of the component fq_pie. The manipulation of the argument quantum/deficit with an unknown input leads to a infinite loop vulnerability. Using CWE to declare the problem leads to CWE-835. The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. Impacted is availability. CVE summarizes:
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.
The advisory is available at git.kernel.org. This vulnerability is handled as CVE-2026-90074 since 09/11/2026. The exploitation is known to be easy. Local access is required to approach this attack. Additional levels of successful authentication are required for exploitation. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit.
Upgrading to version 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6 or 7.3-rc1 eliminates this vulnerability. Applying the patch 1f43e4dbc93b7d02761a024d5f895df823c07b72/f7942b2693bc24c7d609a03d06f97bee3b0bd96a/6f1be05faecef4c0f9a008200209f66ef2e133f7/435da3734a8e63d3067016accc977ed1d10aaaa0/44dad8fe99b58a7fe2961e9eec6a5f07ace5b51f/044fa2498bbc2900f0c48a6ef2fdd5b2bdfc3795/bf97fd2163ad1191ef8daa3d4df8372aee19e396/c86cd7ed0b0e44779a3d1683f03e4353baf4bdc9 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
- 5.10.269
- 5.15.220
- 6.1.187
- 6.6.156
- 6.12.109
- 6.18.0
- 6.18.1
- 6.18.2
- 6.18.3
- 6.18.4
- 6.18.5
- 6.18.6
- 6.18.7
- 6.18.8
- 6.18.9
- 6.18.10
- 6.18.11
- 6.18.12
- 6.18.13
- 6.18.14
- 6.18.15
- 6.18.16
- 6.18.17
- 6.18.18
- 6.18.19
- 6.18.20
- 6.18.21
- 6.18.22
- 6.18.23
- 6.18.24
- 6.18.25
- 6.18.26
- 6.18.27
- 6.18.28
- 6.18.29
- 6.18.30
- 6.18.31
- 6.18.32
- 6.18.33
- 6.18.34
- 6.18.35
- 6.18.36
- 6.18.37
- 6.18.38
- 6.18.39
- 6.18.40
- 6.18.41
- 6.18.42
- 6.18.43
- 6.18.44
- 6.18.45
- 6.18.46
- 6.18.47
- 6.18.48
- 6.18.49
- 6.18.50
- 6.18.51
- 7.2.0
- 7.2.1
- 7.2.2
- 7.2.3
- 7.2.4
- 7.2.5
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.2VulDB Meta Temp Score: 4.0
VulDB Base Score: 4.2
VulDB Temp Score: 4.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Infinite loopCWE: CWE-835 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 5.10.270/5.15.221/6.1.188/6.6.157/6.12.110/6.18.52/7.2.6/7.3-rc1
Patch: 1f43e4dbc93b7d02761a024d5f895df823c07b72/f7942b2693bc24c7d609a03d06f97bee3b0bd96a/6f1be05faecef4c0f9a008200209f66ef2e133f7/435da3734a8e63d3067016accc977ed1d10aaaa0/44dad8fe99b58a7fe2961e9eec6a5f07ace5b51f/044fa2498bbc2900f0c48a6ef2fdd5b2bdfc3795/bf97fd2163ad1191ef8daa3d4df8372aee19e396/c86cd7ed0b0e44779a3d1683f03e4353baf4bdc9
Timeline
09/11/2026 CVE reserved09/17/2026 Advisory disclosed
09/17/2026 VulDB entry created
09/17/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-90074 (🔒)
GCVE (CVE): GCVE-0-2026-90074
GCVE (VulDB): GCVE-100-406562
Entry
Created: 09/17/2026 18:47Changes: 09/17/2026 18:47 (61)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.