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-23254net: gro: fix outer network offset

Description

In the Linux kernel, the following vulnerability has been resolved: net: gro: fix outer network offset The udp GRO complete stage assumes that all the packets inserted the RX have the `encapsulation` flag zeroed. Such assumption is not true, as a few H/W NICs can set such flag when H/W offloading the checksum for an UDP encapsulated traffic, the tun driver can inject GSO packets with UDP encapsulation and the problematic layout can also be created via a veth based setup. Due to the above, in the problematic scenarios, udp4_gro_complete() uses the wrong network offset (inner instead of outer) to compute the outer UDP header pseudo checksum, leading to csum validation errors later on in packet processing. Address the issue always clearing the encapsulation flag at GRO completion time. Such flag will be set again as needed for encapsulated packets by udp_gro_complete().

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 2 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-23254, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% 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: Medium 5.5.

Affected products

  • Linux · Linux

    • affected af276a5ac8e938c8b058e3e124073cc1e322d98b – < 9d40a85138568696387ef04cd004c64612a70874
    • affected 5ef31ea5d053a8f493a772ebad3f3ce82c35d845 – < b83557bc6f560433fe5d727e241069f8db5ba709
    • affected 5ef31ea5d053a8f493a772ebad3f3ce82c35d845 – < 2e5edb69e5d0e23ef248c56fc977039268c77a7b
    • affected 5ef31ea5d053a8f493a772ebad3f3ce82c35d845 – < 5c2c3c38be396257a6a2e55bd601a12bb9781507
    • affected dbd9466d323a72e22efe09151253d195d36d3bf6
    • affected 6.6.31 – < 6.6.124
    • affected 6.8.10 – < 6.9
  • Linux · Linux

    • affected 6.9
    • unaffected < 6.9
    • unaffected 6.6.124 – ≤ 6.6.*
    • unaffected 6.12.70 – ≤ 6.12.*
    • unaffected 6.18.10 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References4

Sources

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

Badge for a README or a ticket

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

Record last updated .