ipvs: bound LBLCR and LBLC cache growth
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 6316d17324bd4ca400c26adb7b656c6e3447c209| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel IPVS LBLCR and LBLC schedulers can create cache entries for previously unseen destination addresses beyond their configured table limit. An attacker who can send traffic using new destination addresses and continue using those entries can cause the caches to keep growing.
Engineers running Linux kernels that use the IPVS LBLCR or LBLC schedulers should check whether their kernel includes this fix; affected versions were not provided.