CVE-2026-97598

ipv4: fib: bound automatic table ID allocation

N/A
Published: September 25, 2026 at 10:22 AM UTC
Updated: October 19, 2026 at 10:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: ipv4: fib: bound automatic table ID allocation fib_empty_table() probes every table ID from 1 until it finds a free one. IPv4 tables are stored in a 256-bucket hash table, so a dense set of IDs makes each probe walk a growing hash chain while RTNL is held. Automatic table assignment ("ip rule ... table 0") is an IPv4-only legacy path. Bound the automatically allocated ID to 4096 so the RTNL hold stays bounded, without changing lookups of explicitly specified table IDs. This changes user-visible behavior. A table-0 rule previously received the lowest free ID in 1..RT_TABLE_MAX (0xFFFFFFFF). After this patch the search stops at 4096 and the rule add fails with ENOBUFS if that range is fully occupied. Explicit table IDs above 4096 remain usable. The automatic path is unused in practice: it is IPv4-only, not documented by ip-rule, uncovered by kernel selftests, and both NetworkManager and systemd refuse table 0.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.19b801f54917b7c6e8540f877ee562cd0725e62ebd
Vendor states this is fixed in 125890702ef4417cd0ffac2e448c0cd4fbf0ac45 (fixed)
Vendor states this is fixed in 2c29c053a6627dc4f12fcfe6b4860bcd9e5d7503 (fixed)
Vendor states this is fixed in 3080f9e653d8c057d5652db5ced8137f81b3fcbd (fixed)
Vendor states this is fixed in 999bc00588cb305ab25065e8a8ac31da7465301c (fixed)
Vendor states this is fixed in bc8d01d856db106f284b19961af6112e10c3e3b4 (fixed)
Vendor states this is fixed in efdfb1e27a3328085b79540dfe781d537b576ea1 (fixed)
Vendor states this is fixed in f1f2da33eaab54b4d5cdea6d70befb2e2fb49cb6 (fixed)
Vendor states this is fixed in fe9a906d2bff2d2707bafd6353b5e032a42aeb35 (fixed)
Vendor states this is fixed in 2.6.19 (unaffected)
Vendor states this is fixed in 5.10.271 (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2.7 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc3 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card