PULSE
FEED
ransomqilin reclama a SEPIVER · MX · Not Foundransomlockbit5 reclama a istanbultrading.com · TR · Retail & E-Commerceransomsilentransomgroup reclama a M... C... · Not Foundransomqilin reclama a United Restaurant Supply · US · Hospitalityransombravox reclama a AMSAM · FR · Not Foundransombravox reclama a Barrow & Grimm · US · Not Foundransomsilentransomgroup reclama a M...r · Not Foundransomsilentransomgroup reclama a Kirkland & Ellis LLP · US · Professional Servicesransomakira reclama a Bethany Press International · Retail & E-Commerceransomakira reclama a Medienwerkstatt · DE · Educationransomakira reclama a Annapath · Not Foundransomrhysida reclama a DR.SCHNELL GmbH & Co. KGaA · DE · Manufacturingransomqilin reclama a Airtificial · Technologyransomqilin reclama a Bathurst RSL · AU · Hospitalityransomqilin reclama a SEPIVER · MX · Not Foundransomlockbit5 reclama a istanbultrading.com · TR · Retail & E-Commerceransomsilentransomgroup reclama a M... C... · Not Foundransomqilin reclama a United Restaurant Supply · US · Hospitalityransombravox reclama a AMSAM · FR · Not Foundransombravox reclama a Barrow & Grimm · US · Not Foundransomsilentransomgroup reclama a M...r · Not Foundransomsilentransomgroup reclama a Kirkland & Ellis LLP · US · Professional Servicesransomakira reclama a Bethany Press International · Retail & E-Commerceransomakira reclama a Medienwerkstatt · DE · Educationransomakira reclama a Annapath · Not Foundransomrhysida reclama a DR.SCHNELL GmbH & Co. KGaA · DE · Manufacturingransomqilin reclama a Airtificial · Technologyransomqilin reclama a Bathurst RSL · AU · Hospitality
← All CVEs
CVE WatchOct 19, 2026

CVE-2026-98234

In the Linux kernel, the following vulnerability has been resolved: net/sched: hhf: cap hh_flows_limit at change time hhf_change() stores

CVSS

—

No CVSS

EPSS

0.2%

p7

KEV

—

Exploit Today

2

0-100

Published: Oct 6, 2026 · Last modified: Oct 19, 2026

EPSS · 30d
0.2%EPSS · 30 days0.2%
2026-10-062026-10-21
Technical description

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.

Official references
Related CVEs

No related CVEs by CWE or product.