CVE-2025-38148
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-401
- Record status
- Analyzed
Affected
- Linux Kernel < 5.15.192
- Linux Kernel < 6.1.142
- Linux Kernel < 6.6.94
- Linux Kernel < 6.12.34
- Linux Kernel < 6.15.3
- Debian Linux 11.0
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-38148.md and follow it. Check whether this project is affected by CVE-2025-38148. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/0b40aeaf83ca04d4c9801e235b7533400c8b5f17
- https://git.kernel.org/stable/c/24b24295464f25fb771d36ed558c7cd942119361
- https://git.kernel.org/stable/c/66abe22017522dd56b820e41ca3a5b131a637001
- https://git.kernel.org/stable/c/846992645b25ec4253167e3f931e4597eb84af56
- https://git.kernel.org/stable/c/cdbabd316c5a4a9b0fda6aafe491e2db17fbb95d
- https://git.kernel.org/stable/c/db2a12ddd3a31f668137ff6a4befc1343c79cbc4
References
- https://git.kernel.org/stable/c/0b40aeaf83ca04d4c9801e235b7533400c8b5f17
- https://git.kernel.org/stable/c/24b24295464f25fb771d36ed558c7cd942119361
- https://git.kernel.org/stable/c/66abe22017522dd56b820e41ca3a5b131a637001
- https://git.kernel.org/stable/c/846992645b25ec4253167e3f931e4597eb84af56
- https://git.kernel.org/stable/c/cdbabd316c5a4a9b0fda6aafe491e2db17fbb95d
- https://git.kernel.org/stable/c/db2a12ddd3a31f668137ff6a4befc1343c79cbc4
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html