CVE-2026-43057: net: correctly handle tunneled traffic on IPV6_CSUM GSO fallback
In the Linux kernel, the following vulnerability has been resolved:
net: correctly handle tunneled traffic on IPV6_CSUM GSO fallback
NETIF_F_IPV6_CSUM only advertises support for checksum offload of
packets without IPv6 extension headers. Packets with extension
headers must fall back onto software checksumming. Since TSO
depends on checksum offload, those must revert to GSO.
The below commit introduces that fallback. It always checks
network header length. For tunneled packets, the inner header length
must be checked instead. Extend the check accordingly.
A special case is tunneled packets without inner IP protocol. Such as
RFC 6951 SCTP in UDP. Those are not standard IPv6 followed by
transport header either, so also must revert to the software GSO path.
Security readout for executives and security teams
Plain-English summary
A Linux networking flaw can mishandle certain tunneled IPv6 packets when hardware checksum offload falls back to software processing. The resulting failure can disrupt system or network availability. The supplied CVSS score is 7.5 because network access, privileges, and user interaction are not required, but the source bundle does not describe the precise failure outcome.
Executive priority
Treat this as a high-priority availability issue for Linux network infrastructure using IPv6 tunneling or offload features. Accelerate vendor confirmation and patching on gateways and shared platforms. Routine Linux endpoints without relevant traffic paths may be lower priority, but should remain in the standard kernel update program.
Technical view
The kernel incorrectly checks the outer network-header length during IPV6_CSUM fallback for tunneled traffic. It should inspect the inner header. IPv6 extension headers and tunnels without an inner IP protocol, including SCTP-over-UDP, must use software GSO because TSO depends on checksum offload. Incorrect fallback handling creates an availability risk.
Likely exposure
Exposure is most plausible on Linux systems processing tunneled IPv6 traffic with checksum offload and GSO/TSO paths enabled. Gateways, virtualized networking hosts, appliances, and container infrastructure may warrant priority review. The supplied version metadata is internally inconsistent, so determine exposure using kernel or distribution advisories rather than version numbers alone.
Exploitation context
The CVSS vector describes network-reachable, low-complexity exploitation without authentication or user interaction, affecting availability only. However, the bundle provides no exploit narrative, proof of concept, or confirmed attack reports. The CVE is not listed as KEV in the supplied data, so active exploitation is not established.
Researcher notes
The record identifies the faulty header-length selection and required software-GSO fallback, but supplies no CWE, crash trace, reproducer, or demonstrated impact mechanism. Its flattened affected-version data appears contradictory, listing later releases as affected while earlier releases appear under an unaffected default. Branch-specific commit ancestry and distribution backports require independent confirmation.
Mitigation direction
Apply the vendor-supported kernel update containing the referenced stable correction.
Consult the Linux distribution or appliance vendor for authoritative affected-version and backport status.
Prioritize internet-facing gateways and systems that process tunneled IPv6 traffic.
If an update is unavailable, request vendor-approved mitigations; none are specified in the supplied sources.
Validation and detection
Inventory kernel builds on systems handling IPv6 tunnels, overlays, or SCTP-over-UDP traffic.
Compare each build against its distribution advisory and the referenced stable kernel commits.
Confirm whether checksum offload, TSO, and GSO are used on relevant network interfaces.
After updating, verify the vendor package includes the correction and perform safe network regression testing.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-43057 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
9Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.