CVE-2026-98857: Linux kernel · ipvs: bound LBLCR and LBLC cache growth
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in bc9ff8e64771cc32a216953fe615386f46ac1eaa : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:18 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in bc9ff8e64771cc32a216953fe615386f46ac1eaa, 31028d7b970962fbeda1e9131405c76551094300, 6316d17324bd4ca400c26adb7b656c6e3447c209 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 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– |
Description
In the Linux kernel, the following vulnerability has been resolved: ipvs: bound LBLCR and LBLC cache growth ip_vs_lblcr_new() and ip_vs_lblc_new() create cache entries for every previously unseen destination address. The table max_size only tells the periodic collector to reclaim entries after the cache has already exceeded the limit. It does not reclaim entries that the attacker continues to use. Reject new cache entries once either table reaches max_size * 3 / 2. The extra headroom lets the periodic collector catch up while the existing scheduler fallback continues to use the selected destination when cache creation fails. New traffic therefore stays serviceable without growing the tables further.
References
- git.kernel.org/stable/c/bc9ff8e64771cc32a216953fe615386f46ac1eaa (opens in a new tab)
- git.kernel.org/stable/c/31028d7b970962fbeda1e9131405c76551094300 (opens in a new tab)
- git.kernel.org/stable/c/6316d17324bd4ca400c26adb7b656c6e3447c209 (opens in a new tab)
- git.kernel.org/stable/c/16c83c047ecfaf226ad81d45d77fa11a3184d0e4 (opens in a new tab)
- git.kernel.org/stable/c/2a3c3de660f96865f303fd25f1285f2ffbfd521d (opens in a new tab)