CVE-2025-38148 [Medium] | Information Disclosure in Linux Kernel

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-04-29	0.04%	0.10%	+0.06%
2	2025-12-18	0.06%	0.04%	-0.01%
3	2025-12-11	—	0.06%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-04-29

0.04%

0.10%

+0.06%

2025-12-18

0.06%

0.04%

-0.01%

2025-12-11

—

0.06%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

[email protected]

OS Trackers for CVE-2025-38148

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2025-38148 not yet assigned priority: Debian including 2 source packages (linux, linux-6.1), 6 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5, open 1.	https://security-tracker.debian.org/tracker/CVE-2025-38148
`redhat`	low	—	https://access.redhat.com/security/cve/CVE-2025-38148
`suse`	medium	CVE-2025-38148 severity moderate: SUSE including 476 source package names (2.1.3-6.67:kernel-default-base-6.4.0-32.1.21.10, 2.1.3-7.44:kernel-default-6.4.0-32.1, …), 1108 product×package rows across 216 product lines (Container suse/sl-micro/6.0/base-os-container, Container suse/sl-micro/6.0/kvm-os-container, … (216 product lines)): Fixed 627, Known Affected 231, Known Not Affected 229, First Fixed 21.	https://www.suse.com/security/cve/CVE-2025-38148/
`ubuntu`	medium	CVE-2025-38148 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, released 169, ignored 164, not-affected 67, needed 3, needs-triage 2, pending 1.	https://ubuntu.com/security/CVE-2025-38148

Affected software / configurations for CVE-2025-38148

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 5.9, < 5.15.192	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 6.1.142	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.2, < 6.6.94	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.7, < 6.12.34	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.13, < 6.15.3	cpe:2.3:o:linux:linux_kernel::::::::
debian	debian_linux	11.0	cpe:2.3:o:debian:debian_linux:11.0:::::::*

References for CVE-2025-38148

URL	Tags
https://git.kernel.org/stable/c/0b40aeaf83ca04d4c9801e235b7533400c8b5f17	Patch
https://git.kernel.org/stable/c/24b24295464f25fb771d36ed558c7cd942119361	Patch
https://git.kernel.org/stable/c/66abe22017522dd56b820e41ca3a5b131a637001	Patch
https://git.kernel.org/stable/c/846992645b25ec4253167e3f931e4597eb84af56	Patch
https://git.kernel.org/stable/c/cdbabd316c5a4a9b0fda6aafe491e2db17fbb95d	Patch
https://git.kernel.org/stable/c/db2a12ddd3a31f668137ff6a4befc1343c79cbc4	Patch
https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html	Third Party Advisory

URL

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

Exploit prediction scoring system (EPSS) score for CVE-2025-38148

Common vulnerability scoring system (CVSS) metrics for CVE-2025-38148

Weakness enumeration for CVE-2025-38148

OS Trackers for CVE-2025-38148

Affected software / configurations for CVE-2025-38148

References for CVE-2025-38148