Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 12 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8b93288b4543ad5139a25a5b211a07bf755652dd
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < f6e9446bfb79907d3092fc45a0054b0c3b329bfe
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 488eaba207dd2e4c5afc65e18dc237d70f01d283
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < bc9ff8e64771cc32a216953fe615386f46ac1eaa
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 31028d7b970962fbeda1e9131405c76551094300
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 6316d17324bd4ca400c26adb7b656c6e3447c209
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 16c83c047ecfaf226ad81d45d77fa11a3184d0e4
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2a3c3de660f96865f303fd25f1285f2ffbfd521d
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.56 – ≤ 6.18.*
    • unaffected 7.2.10 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98857 badge
[![CVE-2026-98857](https://cveledger.app/badge/CVE-2026-98857.svg)](https://cveledger.app/cve/CVE-2026-98857)

Record last updated .