Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-43057net: correctly handle tunneled traffic on IPV6_CSUM GSO fallback

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-43057, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.44% · top 61% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Affected products

  • Linux · Linux

    • affected a0478d7e888028f85fa7785ea838ce0ca09398e2 – < 2094a7cf91b71367b649f991aacc7b579f793d0b
    • affected 2156d9e9f2e483c8c3906c0ea57ea312c1424235 – < ed71cf465c75f5688b07a35d373cd1d6b589c8ea
    • affected 041e2f945f82fdbd6fff577b79c33469430297aa – < 33670f780e0120c3dacda188c512bbffe0b6044c
    • affected 864e3396976ef41de6cc7bc366276bf4e084fff2 – < a98b78116a27e2a57b696b569b2cb431c95cf9b6
    • affected 864e3396976ef41de6cc7bc366276bf4e084fff2 – < 732fdeb2987c94b439d51f5cb9addddc2fc48c42
    • affected 864e3396976ef41de6cc7bc366276bf4e084fff2 – < c4336a07eb6b2526dc2b62928b5104b41a7f81f5
    • affected 794ddbb7b63b6828c75967b9bcd43b086716e7a1
    • affected 6.1.149 – < 6.1.168
    • affected 6.6.103 – < 6.6.134
    • affected 6.12.44 – < 6.12.81
    • affected 6.16.4 – < 6.17
  • Linux · Linux

    • affected 6.17
    • unaffected < 6.17
    • unaffected 6.1.168 – ≤ 6.1.*
    • unaffected 6.6.134 – ≤ 6.6.*
    • unaffected 6.12.81 – ≤ 6.12.*
    • unaffected 6.18.22 – ≤ 6.18.*
    • unaffected 6.19.12 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-43057 badge
[![CVE-2026-43057](https://cveledger.app/badge/CVE-2026-43057.svg)](https://cveledger.app/cve/CVE-2026-43057)

Record last updated .