CVE-2025-38148: net: phy: mscc: Fix memory leak when using one step timestamping
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 Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1
Event History
Frequently Asked Questions
What is the severity of CVE-2025-38148?
CVE-2025-38148 has a low severity rating due to its specific impact on memory leakage during one-step timestamping.
How do I fix CVE-2025-38148?
To fix CVE-2025-38148, ensure your Linux kernel is updated to the latest version that includes the patch for this vulnerability.
What is the impact of CVE-2025-38148?
CVE-2025-38148 can lead to a memory leak when using one-step timestamping, potentially leading to performance degradation.
Which versions of the Linux kernel are affected by CVE-2025-38148?
CVE-2025-38148 affects specific versions of the Linux kernel prior to the implementation of the memory leak fix.
Can CVE-2025-38148 be exploited remotely?
CVE-2025-38148 is not exploitably remote but could affect systems running vulnerable versions of the Linux kernel under specific conditions.