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-2025-40337net: stmmac: Correctly handle Rx checksum offload errors

Description

In the Linux kernel, the following vulnerability has been resolved: net: stmmac: Correctly handle Rx checksum offload errors The stmmac_rx function would previously set skb->ip_summed to CHECKSUM_UNNECESSARY if hardware checksum offload (CoE) was enabled and the packet was of a known IP ethertype. However, this logic failed to check if the hardware had actually reported a checksum error. The hardware status, indicating a header or payload checksum failure, was being ignored at this stage. This could cause corrupt packets to be passed up the network stack as valid. This patch corrects the logic by checking the `csum_none` status flag, which is set when the hardware reports a checksum error. If this flag is set, skb->ip_summed is now correctly set to CHECKSUM_NONE, ensuring the kernel's network stack will perform its own validation and properly handle the corrupt packet.

Timeline

  1. ID reserved

    By Linux

  2. · 8 months later

    Published

  3. · 11 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-2025-40337, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.2CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
NVDNVD · Deferred3.1High8.2CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
EPSS (exploitation in 30 days)
0.52% · top 56% of all CVEs (12 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 3c20f72f9108b2fcf30ec63d8a4203736c01ccd0 – < 3c5e5fccc4138c072d99be4ebe6b16df6a70a40c
    • affected 3c20f72f9108b2fcf30ec63d8a4203736c01ccd0 – < 63fbe0e6413279d5ea5842e2423e351ded547683
    • affected 3c20f72f9108b2fcf30ec63d8a4203736c01ccd0 – < 719fcdf29051f7471d5d433475af76219019d33d
    • affected 3c20f72f9108b2fcf30ec63d8a4203736c01ccd0 – < 1aa319e0f12d2d761a31556b82a5852c98eb0bea
    • affected 3c20f72f9108b2fcf30ec63d8a4203736c01ccd0 – < ee0aace5f844ef59335148875d05bec8764e71e8
  • Linux · Linux

    • affected 3.2
    • unaffected < 3.2
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.117 – ≤ 6.6.*
    • unaffected 6.12.58 – ≤ 6.12.*
    • unaffected 6.17.8 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .