Skip to main content
VulnerabilityPublished Updated

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

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in db2a12ddd3a31f668137ff6a4befc1343c79cbc4 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:04 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in db2a12ddd3a31f668137ff6a4befc1343c79cbc4, cdbabd316c5a4a9b0fda6aafe491e2db17fbb95d, 846992645b25ec4253167e3f931e4597eb84af56 +3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 7d272e63e0979d38a6256108adbe462d621c26c5, < db2a12ddd3a31f668137ff6a4befc1343c79cbc4
Fixed in
  • db2a12ddd3a31f668137ff6a4befc1343c79cbc4
LinuxLinuxAffected
  • ≥ 7d272e63e0979d38a6256108adbe462d621c26c5, < cdbabd316c5a4a9b0fda6aafe491e2db17fbb95d
Fixed in
  • cdbabd316c5a4a9b0fda6aafe491e2db17fbb95d
LinuxLinuxAffected
  • ≥ 7d272e63e0979d38a6256108adbe462d621c26c5, < 846992645b25ec4253167e3f931e4597eb84af56
Fixed in
  • 846992645b25ec4253167e3f931e4597eb84af56
LinuxLinuxAffected
  • ≥ 7d272e63e0979d38a6256108adbe462d621c26c5, < 66abe22017522dd56b820e41ca3a5b131a637001
Fixed in
  • 66abe22017522dd56b820e41ca3a5b131a637001
LinuxLinuxAffected
  • ≥ 7d272e63e0979d38a6256108adbe462d621c26c5, < 24b24295464f25fb771d36ed558c7cd942119361
Fixed in
  • 24b24295464f25fb771d36ed558c7cd942119361
LinuxLinuxAffected
  • ≥ 7d272e63e0979d38a6256108adbe462d621c26c5, < 0b40aeaf83ca04d4c9801e235b7533400c8b5f17
Fixed in
  • 0b40aeaf83ca04d4c9801e235b7533400c8b5f17

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.

References

Community reviews

Loading reviews…