CVE-2026-97596 — ipvs: reject invalid states in connection template sync records
In the Linux kernel, the following vulnerability has been resolved: ipvs: reject invalid states in connection template sync records IPVS sync receivers validate protocol states before creating or updating a connection. For connection templates, however, they only log states outside the template state range and still store the value in the connection. A template can be returned by ordinary connection lookup. TCP and SCTP then use the invalid state as an index into their transition tables. Reject invalid template states in both sync protocol versions before looking up or modifying a connection. The version 1 path handles both IPv4 and IPv6 records.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 275411430f892407b885be1de2548b2e632892c3 and < 5677e81ffdbfc1c03dcb427fb8b1c38289bed76d≥ 275411430f892407b885be1de2548b2e632892c3 and < d4eb339b442a0ffaa565779b975494a0a0664f18≥ 275411430f892407b885be1de2548b2e632892c3 and < 1a8f15911352bb3cf4663aa02049c49c7f30e524≥ 275411430f892407b885be1de2548b2e632892c3 and < 652d9caa5ac925ab012834e325d77b9ed638d4fc≥ 275411430f892407b885be1de2548b2e632892c3 and < fc10dc4511e6e2e2b4098ee115c8e5639471f23d≥ 275411430f892407b885be1de2548b2e632892c3 and < 50c3f06222eafe9cca7ca51a0ef83311d7cab353≥ 275411430f892407b885be1de2548b2e632892c3 and < 0c61f7d8e18a978aec2a16d9acd5f682f1c72476≥ 275411430f892407b885be1de2548b2e632892c3 and < 74cb39735b6cd0aff4b5584158f09376fd97aadf and 1 moreversion 4.19 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 16, 2026 · 2 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/d4eb339b442a0ffaa565779b975494a0a0664f18
- git.kernel.org/stable/c/652d9caa5ac925ab012834e325d77b9ed638d4fc
- git.kernel.org/stable/c/50c3f06222eafe9cca7ca51a0ef83311d7cab353
- git.kernel.org/stable/c/5677e81ffdbfc1c03dcb427fb8b1c38289bed76d
- git.kernel.org/stable/c/0c61f7d8e18a978aec2a16d9acd5f682f1c72476
- git.kernel.org/stable/c/1a8f15911352bb3cf4663aa02049c49c7f30e524
- git.kernel.org/stable/c/74cb39735b6cd0aff4b5584158f09376fd97aadf
- git.kernel.org/stable/c/fc10dc4511e6e2e2b4098ee115c8e5639471f23d
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 1d
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 2d
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 2d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 2d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-97596 is "ipvs: reject invalid states in connection template sync records", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.