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.
- Published
- Sep 25, 2026
- Updated
- Sep 25, 2026
- EPSS
- 0.2% · 9th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Affected systems
—
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
- 4.19affected
- 275411430f892407b885be1de2548b2e632892c3 and later · before fc10dc4511e6e2e2b4098ee115c8e5639471f23daffected · git
- 275411430f892407b885be1de2548b2e632892c3 and later · before 50c3f06222eafe9cca7ca51a0ef83311d7cab353affected · git
- 275411430f892407b885be1de2548b2e632892c3 and later · before 0c61f7d8e18a978aec2a16d9acd5f682f1c72476affected · git
- 275411430f892407b885be1de2548b2e632892c3 and later · before 74cb39735b6cd0aff4b5584158f09376fd97aadfaffected · git
- before 4.19not affected · semver
- 6.12.111 and later · up to and including 6.12.*not affected · semver
- 6.18.53 and later · up to and including 6.18.*not affected · semver
- 7.2.7 and later · up to and including 7.2.*not affected · semver
- 7.3-rc3 and laternot affected · original_commit_for_fix
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 | all versions | — |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-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
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
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 | 0c61f7d8e18a978aec2a16d9acd5f682f1c72476 | Vendor (CNA) |
| Linux Linux | 50c3f06222eafe9cca7ca51a0ef83311d7cab353 | Vendor (CNA) |
| Linux Linux | 74cb39735b6cd0aff4b5584158f09376fd97aadf | Vendor (CNA) |
| Linux Linux | fc10dc4511e6e2e2b4098ee115c8e5639471f23d | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.111-1 · Debian:13 | 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.
No dated events beyond publication.
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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/0c61f7d8e18a978aec2a16d9acd5f682f1c72476
- git.kernel.org/stable/c/50c3f06222eafe9cca7ca51a0ef83311d7cab353
- git.kernel.org/stable/c/74cb39735b6cd0aff4b5584158f09376fd97aadf
- git.kernel.org/stable/c/fc10dc4511e6e2e2b4098ee115c8e5639471f23d
Vendor advisories and official records. Exploit/PoC links are deliberately left out.