CVE-2026-97598: Linux kernel · ipv4: fib: bound automatic table ID allocation
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in fe9a906d2bff2d2707bafd6353b5e032a42aeb35 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:38 UTC
Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in fe9a906d2bff2d2707bafd6353b5e032a42aeb35, f1f2da33eaab54b4d5cdea6d70befb2e2fb49cb6, efdfb1e27a3328085b79540dfe781d537b576ea1 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel at the specified commits. Users should update to a kernel version including these fixes to resolve the issue. Since the automatic table ID allocation path is legacy and unused by common tools, no additional mitigation is typically required.
Description
CVE-2026-97598 addresses a vulnerability in the Linux kernel's IPv4 routing table ID allocation mechanism. The automatic allocation of table IDs for IPv4 rules previously searched the entire range up to RT_TABLE_MAX (0xFFFFFFFF), potentially causing unbounded delays while holding the RTNL lock. The fix bounds this search to 4096, limiting the lock hold duration and changing user-visible behavior by causing rule addition to fail with ENOBUFS if the range is exhausted. This automatic allocation path is legacy, IPv4-only, undocumented, and unused by major components like NetworkManager and systemd.
References
- git.kernel.org/stable/c/999bc00588cb305ab25065e8a8ac31da7465301c (opens in a new tab)
- git.kernel.org/stable/c/f1f2da33eaab54b4d5cdea6d70befb2e2fb49cb6 (opens in a new tab)
- git.kernel.org/stable/c/125890702ef4417cd0ffac2e448c0cd4fbf0ac45 (opens in a new tab)
- git.kernel.org/stable/c/3080f9e653d8c057d5652db5ced8137f81b3fcbd (opens in a new tab)
- git.kernel.org/stable/c/bc8d01d856db106f284b19961af6112e10c3e3b4 (opens in a new tab)
- git.kernel.org/stable/c/fe9a906d2bff2d2707bafd6353b5e032a42aeb35 (opens in a new tab)
- git.kernel.org/stable/c/2c29c053a6627dc4f12fcfe6b4860bcd9e5d7503 (opens in a new tab)
- git.kernel.org/stable/c/efdfb1e27a3328085b79540dfe781d537b576ea1 (opens in a new tab)