CVE-2026-98857: ipvs: bound LBLCR and LBLC cache growth
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Fixed version: Linux Linux 16c83c047ecfaf226ad81d45d77fa11a3184d0e4, 2a3c3de660f96865f303fd25f1285f2ffbfd521d, 31028d7b970962fbeda1e9131405c76551094300; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1.
Low priority for now. Upgrade to Linux Linux 16c83c047ecfaf226ad81d45d77fa11a3184d0e4, 2a3c3de660f96865f303fd25f1285f2ffbfd521d, 31028d7b970962fbeda1e9131405c76551094300; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 18, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 8b93288b4543ad5139a25a5b211a07bf755652ddaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before f6e9446bfb79907d3092fc45a0054b0c3b329bfeaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 488eaba207dd2e4c5afc65e18dc237d70f01d283affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before bc9ff8e64771cc32a216953fe615386f46ac1eaaaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 31028d7b970962fbeda1e9131405c76551094300affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 6316d17324bd4ca400c26adb7b656c6e3447c209affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 16c83c047ecfaf226ad81d45d77fa11a3184d0e4affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 2a3c3de660f96865f303fd25f1285f2ffbfd521daffected · git
- before 2.6.12not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.10-1 | 7.2.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98855Oct 18, 2026 · of/overlay: put property on deadprops only after changeset add succeeds0Monitor
- ← EarlierCVE-2026-98856Oct 18, 2026 · kprobes: Skip disarmed probes when checking optkprobe overlap0Monitor
- Later →CVE-2026-98858Oct 18, 2026 · io_uring: fix task_work add use-after-free with SQPOLL0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 16c83c047ecfaf226ad81d45d77fa11a3184d0e4 | Vendor (CNA) |
| Linux Linux | 2a3c3de660f96865f303fd25f1285f2ffbfd521d | Vendor (CNA) |
| Linux Linux | 31028d7b970962fbeda1e9131405c76551094300 | Vendor (CNA) |
| Linux Linux | 488eaba207dd2e4c5afc65e18dc237d70f01d283 | Vendor (CNA) |
| Linux Linux | 6316d17324bd4ca400c26adb7b656c6e3447c209 | Vendor (CNA) |
| Linux Linux | 8b93288b4543ad5139a25a5b211a07bf755652dd | Vendor (CNA) |
| Linux Linux | bc9ff8e64771cc32a216953fe615386f46ac1eaa | Vendor (CNA) |
| Linux Linux | f6e9446bfb79907d3092fc45a0054b0c3b329bfe | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | 6.6.161.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 10, 2026+23 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2a3c3de660f96865f303fd25f1285f2ffbfd521d
- git.kernel.org/stable/c/31028d7b970962fbeda1e9131405c76551094300
- git.kernel.org/stable/c/488eaba207dd2e4c5afc65e18dc237d70f01d283
- git.kernel.org/stable/c/6316d17324bd4ca400c26adb7b656c6e3447c209
- git.kernel.org/stable/c/8b93288b4543ad5139a25a5b211a07bf755652dd
- git.kernel.org/stable/c/bc9ff8e64771cc32a216953fe615386f46ac1eaa
- git.kernel.org/stable/c/f6e9446bfb79907d3092fc45a0054b0c3b329bfe
Vendor advisories and official records. Exploit/PoC links are deliberately left out.