CVE-2025-38148

net: phy: mscc: Fix memory leak when using one step timestamping

MEDIUM

5.5

CVSS Score

Published: July 3, 2025 at 08:35 AM UTC

Updated: June 17, 2026 at 09:16 AM UTC

2 products affected across 2 vendorsLinux KernelDebian Linux

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: phy: mscc: Fix memory leak when using one step timestamping Fix memory leak when running one-step timestamping. When running one-step sync timestamping, the HW is configured to insert the TX time into the frame, so there is no reason to keep the skb anymore. As in this case the HW will never generate an interrupt to say that the frame was timestamped, then the frame will never released. Fix this by freeing the frame in case of one-step timestamping.

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%

5.16 ≤ v < 6.1.1425.9 ≤ v < 5.15.1925.9 ≤ v < 6.1.1425.9 ≤ v < 6.12.345.9 ≤ v < 6.15.35.9 ≤ v < 6.165.9 ≤ v < 6.6.946.13 ≤ v < 6.15.36.2 ≤ v < 6.6.946.7 ≤ v < 6.12.345.97d272e63e0979d38a6256108adbe462d621c26c5

Vendor states this is fixed in 0b40aeaf83ca04d4c9801e235b7533400c8b5f17 (fixed)

Vendor states this is fixed in 24b24295464f25fb771d36ed558c7cd942119361 (fixed)

Vendor states this is fixed in 66abe22017522dd56b820e41ca3a5b131a637001 (fixed)

Vendor states this is fixed in 846992645b25ec4253167e3f931e4597eb84af56 (fixed)

Vendor states this is fixed in cdbabd316c5a4a9b0fda6aafe491e2db17fbb95d (fixed)

Vendor states this is fixed in db2a12ddd3a31f668137ff6a4befc1343c79cbc4 (fixed)

Vendor states this is fixed in 5.15.192 (unaffected)

Vendor states this is fixed in 5.9 (unaffected)

Vendor states this is fixed in 6.1.142 (unaffected)

Vendor states this is fixed in 6.12.34 (unaffected)

Vendor states this is fixed in 6.15.3 (unaffected)

Vendor states this is fixed in 6.16 (unaffected)