CVE-2025-37909

net: lan743x: Fix memleak issue when GSO enabled

MEDIUM

5.5

CVSS Score

Published: May 20, 2025 at 03:21 PM UTC

Updated: October 15, 2026 at 02:17 AM UTC

5 products affected across 3 vendorsLinux KernelDebian LinuxSIMATIC S7-1500 CPU 1518-4 Pn /dp MFP Firmware

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: net: lan743x: Fix memleak issue when GSO enabled Always map the `skb` to the LS descriptor. Previously skb was mapped to EXT descriptor when the number of fragments is zero with GSO enabled. Mapping the skb to EXT descriptor prevents it from being freed, leading to a memory leak

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Debian Linux · Debiandrupal

95%

11.0

Linux Kernel · Linux

95%

4.17 ≤ v < 5.4.2945.11 ≤ v < 5.15.1825.16 ≤ v < 6.1.1385.5 ≤ v < 5.10.2386.13 ≤ v < 6.14.66.2 ≤ v < 6.6.906.7 ≤ v < 6.12.2823f0703c125be490f70501b6b24ed5645775c56a4.17 6.15 6.15 rc1 6.15 rc2 6.15 rc3 6.15 rc4

Vendor states this is fixed in 093855ce90177488eac772de4eefbb909033ce5f (fixed)

Vendor states this is fixed in 189b05f189cac9fd233ef04d31cb5078c4d09c39 (fixed)

Vendor states this is fixed in 2d52e2e38b85c8b7bc00dca55c2499f46f8c8198 (fixed)

Vendor states this is fixed in 6c65ee5ad632eb8dcd3a91cf5dc99b22535f44d9 (fixed)

Vendor states this is fixed in a0e0efbabbbe6a1859bc31bf65237ce91e124b9b (fixed)

Vendor states this is fixed in dae1ce27ceaea7e1522025b15252e3cc52802622 (fixed)

Vendor states this is fixed in df993daa4c968b4b23078eacc248f6502ede8664 (fixed)

Vendor states this is fixed in f42c18e2f14c1b1fdd2a5250069a84bc854c398c (fixed)

Vendor states this is fixed in 4.17 (unaffected)

Vendor states this is fixed in 5.10.238 (unaffected)

Vendor states this is fixed in 5.15.182 (unaffected)

Vendor states this is fixed in 5.4.294 (unaffected)