Live › vulnerability › CVE-2026-98857
Go to dashboardThe Linux kernel's IPVS load balancer creates a cache entry for every new destination address in its LBLC and LBLCR schedulers, and the size limit only triggers cleanup after it is already exceeded. An attacker sending traffic from many addresses can grow these tables without bound, consuming kernel memory.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Only systems running IP Virtual Server (ipvs) with the LBLC or LBLCR scheduler are exposed, typically Linux load balancers in front of services. Hosts that do not use IPVS, or use other schedulers, can skip it. The sources do not say which kernel versions are affected.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-98857")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.