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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.15.192, 6.1.142, 6.12.34, 6.15.3, 6.6.94
- CVEs
- CVE-2025-38148
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 07:32 UTC · Revision 1
Source evidence
net: phy: mscc: Fix memory leak when using one step timestamping
core-osv · Original sourcePublished 3 Jul 2025, 08:35 UTC
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.
osv:CVE-2025-38148
Kernel
Fixed versions: 5.15.192, 6.1.142, 6.6.94, 6.12.34, 6.15.3
Complete source record
{
"id": "5c33b402d8e5d50905efc86417c45252d5305bc90e0c72693ed213c9e2330a17",
"url": "https://osv.dev/vulnerability/CVE-2025-38148",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "net: phy: mscc: Fix memory leak when using one step timestamping",
"summary": "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.",
"evidence": "osv:CVE-2025-38148",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.15.192",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.142",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.94",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.34",
"evidence": "/affected/1/ranges"
},
{
"value": "6.15.3",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2025-38148",
"aliases": [
"CVE-2025-38148"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "7d272e63e0979d38a6256108adbe462d621c26c5"
},
{
"fixed": "24b24295464f25fb771d36ed558c7cd942119361"
},
{
"fixed": "db2a12ddd3a31f668137ff6a4befc1343c79cbc4"
},
{
"fixed": "0b40aeaf83ca04d4c9801e235b7533400c8b5f17"
},
{
"fixed": "66abe22017522dd56b820e41ca3a5b131a637001"
},
{
"fixed": "cdbabd316c5a4a9b0fda6aafe491e2db17fbb95d"
},
{
"fixed": "846992645b25ec4253167e3f931e4597eb84af56"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38148.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.9.0"
},
{
"fixed": "5.15.192"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.142"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.94"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.34"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.15.3"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38148.json"
}
}
],
"modified": "2026-10-28T02:30:50.375514244Z",
"provider": "osv",
"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",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38148.json",
"https://nvd.nist.gov/vuln/detail/CVE-2025-38148",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38148.json"
}
},
"related_cves": [
{
"value": "CVE-2025-38148",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 518654,
"published_at": "2025-07-03T08:35:53.544+00:00"
}