CVE-2026-98857: ipvs: bound LBLCR and LBLC cache growth

Published Oct 18, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

ipvs: bound LBLCR and LBLC cache growth

ipvslblcrnew() and ipvslblcnew() create cache entries for every previously unseen destination address. The table maxsize 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 maxsize 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.

Affected Software

1 affected component
Linux Linux kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    For IPVS LBLCR and LBLC caches, reject new cache entries once either table reaches max_size * 3 / 2, and have the periodic collector reclaim entries when the cache has exceeded its max_size limit.

Event History

Oct 18, 2026
CVE Published
via MITRE·03:51 PM
Data Sourced
via MITRE·03:51 PM
Description
Data Sourced
via NVD·04:17 PM
Description

Frequently Asked Questions

1

Which systems are exposed to unbounded cache growth?

Systems using Linux IPVS with the LBLCR or LBLC scheduler are exposed. The issue occurs when those schedulers receive traffic for previously unseen destination addresses, causing new cache entries to be created.

2

What does an attacker need to do to trigger the issue?

An attacker needs to send traffic that causes the LBLCR or LBLC scheduler to encounter continually new destination addresses while continuing to use entries already created. The periodic collector can reclaim entries only after the configured table limit has been exceeded, and it does not remove entries that remain in use.

3

What happens if cache creation is rejected after the limit is reached?

The scheduler falls back to the selected destination, so new traffic remains serviceable. The fix rejects new cache entries once a table reaches max_size multiplied by 3/2, preventing further table growth while allowing the periodic collector to catch up.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203