EudorIACyber Intelligence
Operational monitoring Newsletter IT EN
← Back to intelligence
Vulnerability

CVE-2026-98104: In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_u32: fix duplicate handle when node ID pool is exhausted gen_new_kid() falls back to returning max (htid | 0xFFF) when both idr_alloc_u32

Official source
EudorIA operational summary

What it means

Priority 45/100

NIST National Vulnerability Database ha pubblicato CVE-2026-98104. La rilevanza va confermata rispetto alle tecnologie effettivamente in uso.

Why it matters

Il segnale diventa operativo solo se prodotto, versione o servizio sono presenti nel perimetro.

AudienceITSOCCISO
Information centre

Translation in progress

NIST National Vulnerability Database

The official content is available in the original language. The Italian version will be published once automated checks are complete.

Text acquired from the source

In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_u32: fix duplicate handle when node ID pool is exhausted gen_new_kid() falls back to returning max (htid | 0xFFF) when both idr_alloc_u32() ranges are full, instead of reporting an error. u32_change() trusts that value and inserts a new knode with a handle that is already live in the hash table, breaking handle uniqueness within the table's node ID space. The handle was never reserved in ht->handle_idr, so every later error path that does idr_remove(&ht->handle_idr, handle) removes the reservation of a different, live knode, which is then reused — one failed add compounds into further duplicates. The 4095 limit is per (table, bucket) — ht->handle_idr is per hash table and the range is derived from htid (bucketid), so a table with divisor 256 can legitimately hold 256*4095 knodes. The sibling helper gen_new_htid() has the same silent in-band failure: it returns 0 when the tp_c handle pool (1..0x7FF) is full, and u32_init() publishes the root hash table with handle 0 without checking. Two root tables with handle 0 alias in u32_lookup_ht(), allowing cross-tcf_proto knode add/lookup/delete. Add the same exhaustion check that the divisor path already has. Return an error so u32_change() fails with ENOSPC/ENOMEM when the node ID space is exhausted, and so u32_init() fails with -ENOMEM when the hash table ID space is exhausted. The extack message distinguishes pool exhaustion (-ENOSPC) from a transient allocation failure (-ENOMEM). Conditions to recreate the bug: - CONFIG_NET_SCHED=y, CONFIG_CLS_U32=y (or =m with module loaded) - Create a clsact qdisc on a device, then add 4095 u32 filters with auto-generated handles to fill the node ID space for the root hash table (single bucket). The 4096th a

Source
NIST National Vulnerability Database
Publishing entity
NIST National Vulnerability Database
Entity type
National authority
Area
North America · US
Original language
en · translation in preparation
Publication
25/09/2026 13:17
CVE
CVE-2026-98104
Stated country
US
Technical scope

Affected products and versions

Not published
No structured range published.

The official sources queried do not yet expose a list of affected versions. No automatic inference is made.

Sources for the versionsNIST National Vulnerability Database
Open the original source