ipvs: use parsed transport offset in SCTP state lookup
In the Linux kernel, the following vulnerability has been resolved: ipvs: use parsed transport offset in SCTP state lookup set_sctp_state() reads the SCTP chunk header again in order to drive the IPVS SCTP state table. For IPv6 it computes the offset with sizeof(struct ipv6hdr), while the surrounding IPVS code uses iph.len from ip_vs_fill_iph_skb(), where ipv6_find_hdr() has already skipped extension headers and found the real transport header. This makes the state machine read from the wrong offset for IPv6 SCTP packets that carry extension headers. For example, an INIT packet with an 8-byte destination options header can be scheduled correctly by sctp_conn_schedule(), but set_sctp_state() reads the first byte of the SCTP verification tag as a DATA chunk type. The connection then moves from NONE to ESTABLISHED instead of INIT1, gets the longer established timeout, and updates the active/inactive destination counters incorrectly. This happens even though the SCTP handshake has not completed. Use the parsed transport offset passed down from ip_vs_set_state() for the SCTP chunk-header lookup. For IPv4 and IPv6 packets without extension headers this preserves the existing offset.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; 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 help- Published
- Aug 15, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.6% · 47th 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
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.2
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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
- 2.6.34affected
- 2906f66a5682e5670a5eefe991843689b8d8563f and later · before d2b8b1557ec07ea1bb5dddbceaf4dfe63d388e27affected · git
- 2906f66a5682e5670a5eefe991843689b8d8563f and later · before 9f94573ab962a9e81954b755da016fa3cd2f5039affected · git
- 2906f66a5682e5670a5eefe991843689b8d8563f and later · before 290e9e8389b556efc603522e28bd1543846aa336affected · git
- 2906f66a5682e5670a5eefe991843689b8d8563f and later · before 9cb5ac594ca76d3a71803b23b74c835b0721e628affected · git
- 2906f66a5682e5670a5eefe991843689b8d8563f and later · before a4a2d2e483d79cc2ad3a170674cf159644acf22baffected · git
- 2906f66a5682e5670a5eefe991843689b8d8563f and later · before 247d055504dcc852e539b9f7f30d19f9741474bfaffected · git
- 2906f66a5682e5670a5eefe991843689b8d8563f and later · before e5d0bb8871668f20de8f3c94b5ae3f372346bc6eaffected · git
- 2906f66a5682e5670a5eefe991843689b8d8563f and later · before 2f75c0faa3361b28e36cc0512b3299e163e25789affected · git
- before 2.6.34not 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 | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-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 | 247d055504dcc852e539b9f7f30d19f9741474bf | Vendor (CNA) |
| Linux Linux | 290e9e8389b556efc603522e28bd1543846aa336 | Vendor (CNA) |
| Linux Linux | 2f75c0faa3361b28e36cc0512b3299e163e25789 | Vendor (CNA) |
| Linux Linux | 9cb5ac594ca76d3a71803b23b74c835b0721e628 | Vendor (CNA) |
| Linux Linux | 9f94573ab962a9e81954b755da016fa3cd2f5039 | Vendor (CNA) |
| Linux Linux | a4a2d2e483d79cc2ad3a170674cf159644acf22b | Vendor (CNA) |
| Linux Linux | d2b8b1557ec07ea1bb5dddbceaf4dfe63d388e27 | Vendor (CNA) |
| Linux Linux | e5d0bb8871668f20de8f3c94b5ae3f372346bc6e | Vendor (CNA) |
| debian:linux | 6.1.180-1 · 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.
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
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
nvd-secondary
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/247d055504dcc852e539b9f7f30d19f9741474bf
- git.kernel.org/stable/c/290e9e8389b556efc603522e28bd1543846aa336
- git.kernel.org/stable/c/2f75c0faa3361b28e36cc0512b3299e163e25789
- git.kernel.org/stable/c/9cb5ac594ca76d3a71803b23b74c835b0721e628
- git.kernel.org/stable/c/9f94573ab962a9e81954b755da016fa3cd2f5039
- git.kernel.org/stable/c/a4a2d2e483d79cc2ad3a170674cf159644acf22b
- git.kernel.org/stable/c/d2b8b1557ec07ea1bb5dddbceaf4dfe63d388e27
- git.kernel.org/stable/c/e5d0bb8871668f20de8f3c94b5ae3f372346bc6e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.