- —Not scoredno CVSS score yet
- 0.22%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 1 day later
· 1 day later
Published
- 24 days later
· 24 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.22% · top 88% of all CVEs (10 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected b801f54917b7c6e8540f877ee562cd0725e62ebd – < 999bc00588cb305ab25065e8a8ac31da7465301c
- affected b801f54917b7c6e8540f877ee562cd0725e62ebd – < f1f2da33eaab54b4d5cdea6d70befb2e2fb49cb6
- affected b801f54917b7c6e8540f877ee562cd0725e62ebd – < 125890702ef4417cd0ffac2e448c0cd4fbf0ac45
- affected b801f54917b7c6e8540f877ee562cd0725e62ebd – < 3080f9e653d8c057d5652db5ced8137f81b3fcbd
- affected b801f54917b7c6e8540f877ee562cd0725e62ebd – < bc8d01d856db106f284b19961af6112e10c3e3b4
- affected b801f54917b7c6e8540f877ee562cd0725e62ebd – < fe9a906d2bff2d2707bafd6353b5e032a42aeb35
- affected b801f54917b7c6e8540f877ee562cd0725e62ebd – < 2c29c053a6627dc4f12fcfe6b4860bcd9e5d7503
- affected b801f54917b7c6e8540f877ee562cd0725e62ebd – < efdfb1e27a3328085b79540dfe781d537b576ea1
- affected 2.6.19
- unaffected < 2.6.19
- unaffected 5.10.271 – ≤ 5.10.*
- unaffected 5.15.222 – ≤ 5.15.*
- unaffected 6.1.189 – ≤ 6.1.*
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.111 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.2.7 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
8
- https://git.kernel.org/stable/c/999bc00588cb305ab25065e8a8ac31da7465301c (opens in a new tab)
- https://git.kernel.org/stable/c/f1f2da33eaab54b4d5cdea6d70befb2e2fb49cb6 (opens in a new tab)
- https://git.kernel.org/stable/c/125890702ef4417cd0ffac2e448c0cd4fbf0ac45 (opens in a new tab)
- https://git.kernel.org/stable/c/3080f9e653d8c057d5652db5ced8137f81b3fcbd (opens in a new tab)
- https://git.kernel.org/stable/c/bc8d01d856db106f284b19961af6112e10c3e3b4 (opens in a new tab)
- https://git.kernel.org/stable/c/fe9a906d2bff2d2707bafd6353b5e032a42aeb35 (opens in a new tab)
- https://git.kernel.org/stable/c/2c29c053a6627dc4f12fcfe6b4860bcd9e5d7503 (opens in a new tab)
- https://git.kernel.org/stable/c/efdfb1e27a3328085b79540dfe781d537b576ea1 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86729 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-97598)Record last updated .