Skip to main content

Linux Kernel CVE-2025-40337

HIGH
2025-12-09 416baaa9-dc9f-4396-8d5f-8c081fb06d67
8.2
CVSS 3.1 · Vendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Share

Severity by source

Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67) PRIMARY
8.2 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
vuln.today AI
3.7 LOW

Network-reachable but requires inducing checksum-failing frames (AC:H); impact is acceptance of corrupt data (I:L), with no confidentiality or availability effect.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
SUSE
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Primary rating from Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67).

CVSS VectorVendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
Low

Lifecycle Timeline

2
Analysis Generated
Jul 30, 2026 - 07:35 vuln.today
CVE Published
Dec 09, 2025 - 16:17 cve.org
HIGH 8.2

DescriptionCVE.org

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.

AnalysisAI

Data-integrity corruption in the Linux kernel's stmmac (Synopsys DesignWare/STMMAC) Ethernet driver allows malformed packets that failed hardware checksum validation to be accepted as valid by the network stack. When hardware checksum offload (CoE) is enabled, the Rx path marked known IP-ethertype frames as CHECKSUM_UNNECESSARY without honoring the hardware's reported header/payload checksum error, so corrupt frames bypass the stack's own validation. There is no public exploit identified at time of analysis, KEV status is not listed, and EPSS is low (0.20%, 11th percentile).

Technical ContextAI

The stmmac driver services the Synopsys DesignWare MAC IP block, which is embedded in many ARM/RISC SoCs and some Intel platforms (STMicroelectronics STi, Rockchip, Amlogic, Allwinner, etc.). Modern MACs support Checksum Offload Engine (CoE), computing IPv4/TCP/UDP checksums in hardware and reporting results via descriptor status bits. In the flawed logic, stmmac_rx() set skb->ip_summed = CHECKSUM_UNNECESSARY whenever CoE was on and the frame was a recognized IP ethertype, ignoring the descriptor's error indication. The root cause is improper validation of a security/integrity-relevant check result (conceptually CWE-354, Improper Validation of Integrity Check Value; no CWE was assigned in the input). The fix consults the csum_none status flag and instead sets CHECKSUM_NONE so the kernel software-validates the packet.

Affected ProductsAI

The affected component is the stmmac network driver in the mainline Linux kernel (drivers/net/ethernet/stmicro/stmmac). No CPE strings or explicit version ranges were provided in the input; the four referenced git.kernel.org/stable commits (1aa319e, 63fbe0e, 719fcdf, ee0aace) indicate the fix was backported across multiple stable branches, implying a broad range of kernel versions with the CoE Rx path is affected until patched. Impact is limited to platforms whose Ethernet is driven by stmmac with hardware checksum offload enabled. Refer to the kernel stable tree commits for the precise affected/patched versions per branch, as no single vendor advisory URL or fixed tag was supplied.

RemediationAI

Upstream fix available (commits/PR); a released patched version is not independently confirmed from the input - apply the kernel update from your distribution or stable branch that includes the stmmac Rx checksum fix, referencing the stable commits at https://git.kernel.org/stable/c/1aa319e0f12d2d761a31556b82a5852c98eb0bea and the sibling backports (63fbe0e6413279d5ea5842e2423e351ded547683, 719fcdf29051f7471d5d433475af76219019d33d, ee0aace5f844ef59335148875d05bec8764e71e8). As a workaround where you cannot immediately patch, you can disable Rx hardware checksum offload on the affected interface with 'ethtool -K <iface> rx off' (and 'rx-checksum off'), which forces the kernel to validate all checksums in software and closes the flaw at the cost of increased CPU utilization on high-throughput links. Do not disable software checksum validation as a mitigation, and prefer the kernel update since the offload workaround only masks the driver bug.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
Container suse/sl-micro/6.0/baremetal-os-container:latest Affected
Container suse/sl-micro/6.0/base-os-container:2.1.3-7.95 Image SL-Micro Affected
Container suse/sl-micro/6.0/kvm-os-container:2.1.3-6.115 Affected
Container suse/sl-micro/6.0/rt-os-container:2.1.3-7.146 Affected
Container suse/sl-micro/6.0/toolbox:latest Affected

Share

CVE-2025-40337 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy