linux-cve-announce - CVE-2025-38148: net: phy: mscc: Fix memory leak when using one step timestamping

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025070336-CVE-2025-38148-76a4@gregkh>
Date: Thu,  3 Jul 2025 10:36:05 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38148: net: phy: mscc: Fix memory leak when using one step timestamping

From: Greg Kroah-Hartman <gregkh@...nel.org>

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.

The Linux kernel CVE team has assigned CVE-2025-38148 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.9 with commit 7d272e63e0979d38a6256108adbe462d621c26c5 and fixed in 6.1.142 with commit db2a12ddd3a31f668137ff6a4befc1343c79cbc4
	Issue introduced in 5.9 with commit 7d272e63e0979d38a6256108adbe462d621c26c5 and fixed in 6.6.94 with commit 0b40aeaf83ca04d4c9801e235b7533400c8b5f17
	Issue introduced in 5.9 with commit 7d272e63e0979d38a6256108adbe462d621c26c5 and fixed in 6.12.34 with commit 66abe22017522dd56b820e41ca3a5b131a637001
	Issue introduced in 5.9 with commit 7d272e63e0979d38a6256108adbe462d621c26c5 and fixed in 6.15.3 with commit cdbabd316c5a4a9b0fda6aafe491e2db17fbb95d
	Issue introduced in 5.9 with commit 7d272e63e0979d38a6256108adbe462d621c26c5 and fixed in 6.16-rc1 with commit 846992645b25ec4253167e3f931e4597eb84af56

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2025-38148
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/net/phy/mscc/mscc_ptp.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/db2a12ddd3a31f668137ff6a4befc1343c79cbc4
	https://git.kernel.org/stable/c/0b40aeaf83ca04d4c9801e235b7533400c8b5f17
	https://git.kernel.org/stable/c/66abe22017522dd56b820e41ca3a5b131a637001
	https://git.kernel.org/stable/c/cdbabd316c5a4a9b0fda6aafe491e2db17fbb95d
	https://git.kernel.org/stable/c/846992645b25ec4253167e3f931e4597eb84af56