Skip to main content
VulnerabilityPublished Updated

CVE-2026-98104: Linux kernel · Unchecked Error Condition

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-98104· Medium

Not known to be exploited · CVSS 5.5 Medium · fixed in feab9261b537df4ebb8350e4779bc185373059fd : update Linux kernel when convenient.

Data as of 17 Nov 2026, 22:49 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in feab9261b537df4ebb8350e4779bc185373059fd, f594f04268d01c5fdc975f3f51fc219ea2159ac6, f4ee13ed7f7b22dcd8287fcf477ae37bd84567da +3
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 7801db8aec957fa6610efe0ee26a6c8bc0f1d73b, < feab9261b537df4ebb8350e4779bc185373059fd
Fixed in
  • feab9261b537df4ebb8350e4779bc185373059fd
LinuxLinuxAffected
  • ≥ 7801db8aec957fa6610efe0ee26a6c8bc0f1d73b, < f594f04268d01c5fdc975f3f51fc219ea2159ac6
Fixed in
  • f594f04268d01c5fdc975f3f51fc219ea2159ac6
LinuxLinuxAffected
  • ≥ 7801db8aec957fa6610efe0ee26a6c8bc0f1d73b, < f4ee13ed7f7b22dcd8287fcf477ae37bd84567da
Fixed in
  • f4ee13ed7f7b22dcd8287fcf477ae37bd84567da
LinuxLinuxAffected
  • ≥ 7801db8aec957fa6610efe0ee26a6c8bc0f1d73b, < d7e7e98d23f42a92d9ab7e36302bd96bd9b33b5f
Fixed in
  • d7e7e98d23f42a92d9ab7e36302bd96bd9b33b5f
LinuxLinuxAffected
  • ≥ 7801db8aec957fa6610efe0ee26a6c8bc0f1d73b, < 84223baf21bc9b008444ae9bc38d5fb91fe00b9d
Fixed in
  • 84223baf21bc9b008444ae9bc38d5fb91fe00b9d
LinuxLinuxAffected
  • ≥ 7801db8aec957fa6610efe0ee26a6c8bc0f1d73b, < 6890e28840bae4f6805e8de981c4ec8e12a4e064
Fixed in
  • 6890e28840bae4f6805e8de981c4ec8e12a4e064

Description

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 auto-handle filter add triggers the duplicate handle (fh 800::fff reused). Reachable at Level 2 (unshare -Urn, namespace-local CAP_NET_ADMIN). - For gen_new_htid: create 2047 u32 proto entries on the same block to fill the tp_c handle pool, then create one more. The root table gets handle 0 and aliases with other handle-0 root tables.

References

Community reviews

Loading reviews…