Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 16 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38148, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 7d272e63e0979d38a6256108adbe462d621c26c5 – < 24b24295464f25fb771d36ed558c7cd942119361
    • affected 7d272e63e0979d38a6256108adbe462d621c26c5 – < db2a12ddd3a31f668137ff6a4befc1343c79cbc4
    • affected 7d272e63e0979d38a6256108adbe462d621c26c5 – < 0b40aeaf83ca04d4c9801e235b7533400c8b5f17
    • affected 7d272e63e0979d38a6256108adbe462d621c26c5 – < 66abe22017522dd56b820e41ca3a5b131a637001
    • affected 7d272e63e0979d38a6256108adbe462d621c26c5 – < cdbabd316c5a4a9b0fda6aafe491e2db17fbb95d
    • affected 7d272e63e0979d38a6256108adbe462d621c26c5 – < 846992645b25ec4253167e3f931e4597eb84af56
  • Linux · Linux

    • affected 5.9
    • unaffected < 5.9
    • unaffected 5.15.192 – ≤ 5.15.*
    • unaffected 6.1.142 – ≤ 6.1.*
    • unaffected 6.6.94 – ≤ 6.6.*
    • unaffected 6.12.34 – ≤ 6.12.*
    • unaffected 6.15.3 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38148 badge
[![CVE-2025-38148](https://cveledger.app/badge/CVE-2025-38148.svg)](https://cveledger.app/cve/CVE-2025-38148)

Record last updated .