CVE-2026-98234net/sched: hhf: cap hh_flows_limit at change time
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: net/sched: hhf: cap hh_flows_limit at change time hhf_change() stores TCA_HHF_HH_FLOWS_LIMIT with no upper bound. A huge hh_flows_limit lets each new heavy-hitter flow pass the hh_flows_current_cnt check in alloc_new_hh() and forces a fixed-size kzalloc(GFP_ATOMIC) per flow under spoofed traffic, for unbounded memory growth. Bound the attribute with NLA_POLICY_MAX() at 2*HH_FLOWS_CNT (the hhf_init() default) and report the rejected value via extack. The deprecated nested parse is kept: legacy tc does not set NLA_F_NESTED on TCA_OPTIONS. Configs relying on hh_limit above the default were relying on unbounded, unsafe behaviour and are not supported going forward. hhf_init() also ran hhf_change() before setting the default hh_flows_limit, so a user-supplied hh_limit at add time was clobbered back to 2048. Set the default before hhf_change() so the configured value sticks. This is a follow-up to commit eb56a495f59b ("net/sched: hhf: clamp quantum in change and init paths"), which bounded the quantum of the same qdisc; the hh_flows_limit bound is the remaining unbounded knob of that series' scope. Conditions to recreate the bug: CAP_NET_ADMIN in a user namespace; tc qdisc change dev X root hhf hh_limit 4294967295 succeeds and the value is echoed by tc qdisc show, unbounding heavy-hitter flow allocations; also tc qdisc add dev X root hhf hh_limit 500 stores 2048 instead of 500.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 6, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | 10239edf86f137ce4c39b62ea9575e8053c549a0 builds before 7adfd0a42174b85c6bd678858ecd6674f403f336; 10239edf86f137ce4c39b62ea9575e8053c549a0 builds before 35fd423a5c5132c6f4321f6c4f0a7b4b90af830c; 10239edf86f137ce4c39b62ea9575e8053c549a0 builds before 06d2a101e89063cb0b9b459104db48bdfb0a797d; from 10239edf86f137ce4c39b62ea9575e8053c549a0 before d8e2f1f0263b7c97b222c06070cccf13e0ab7112; from 10239edf86f137ce4c39b62ea9575e8053c549a0 before f3f4a5cb4a6e9b1f1f25d34dfc25f836a1601db4; 10239edf86f137ce4c39b62ea9575e8053c549a0 builds before 1731ff1d20489afe4cd01b7d16d37f324746ac54; from 10239edf86f137ce4c39b62ea9575e8053c549a0 before f6547d27ce2093c5627636fb63dd0b7523c466f9; 10239edf86f137ce4c39b62ea9575e8053c549a0 builds before 2cef2588c995722a901368def30befeef9ae55c6 | CNA record |
References
- https://git.kernel.org/stable/c/7adfd0a42174b85c6bd678858ecd6674f403f336
- https://git.kernel.org/stable/c/35fd423a5c5132c6f4321f6c4f0a7b4b90af830c
- https://git.kernel.org/stable/c/06d2a101e89063cb0b9b459104db48bdfb0a797d
- https://git.kernel.org/stable/c/d8e2f1f0263b7c97b222c06070cccf13e0ab7112
- https://git.kernel.org/stable/c/f3f4a5cb4a6e9b1f1f25d34dfc25f836a1601db4
- https://git.kernel.org/stable/c/1731ff1d20489afe4cd01b7d16d37f324746ac54
- https://git.kernel.org/stable/c/f6547d27ce2093c5627636fb63dd0b7523c466f9
- https://git.kernel.org/stable/c/2cef2588c995722a901368def30befeef9ae55c6
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.