net: lan743x: fix potential out-of-bounds write in lan743x_ptp_io_event_clock_get()
In the Linux kernel, the following vulnerability has been resolved: net: lan743x: fix potential out-of-bounds write in lan743x_ptp_io_event_clock_get() Before calling lan743x_ptp_io_event_clock_get(), the 'channel' value is checked against the maximum value of PCI11X1X_PTP_IO_MAX_CHANNELS(8). This seems correct and aligns with the PTP interrupt status register (PTP_INT_STS) specifications. However, lan743x_ptp_io_event_clock_get() writes to ptp->extts[] with only LAN743X_PTP_N_EXTTS(4) elements, using channel as an index: lan743x_ptp_io_event_clock_get(..., u8 channel,...) { ... /* Update Local timestamp */ extts = &ptp->extts[channel]; extts->ts.tv_sec = sec; ... } To avoid an out-of-bounds write and utilize all the supported GPIO inputs, set LAN743X_PTP_N_EXTTS to 8. Detected using the static analysis tool - Svace.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.1.142, 6.12.35, 6.15.4, 6.6.95
- CVEs
- CVE-2025-38183
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 23:07 UTC · Revision 1
Source evidence
net: lan743x: fix potential out-of-bounds write in lan743x_ptp_io_event_clock_get()
core-osv · Original sourcePublished 4 Jul 2025, 13:37 UTC
In the Linux kernel, the following vulnerability has been resolved: net: lan743x: fix potential out-of-bounds write in lan743x_ptp_io_event_clock_get() Before calling lan743x_ptp_io_event_clock_get(), the 'channel' value is checked against the maximum value of PCI11X1X_PTP_IO_MAX_CHANNELS(8). This seems correct and aligns with the PTP interrupt status register (PTP_INT_STS) specifications. However, lan743x_ptp_io_event_clock_get() writes to ptp->extts[] with only LAN743X_PTP_N_EXTTS(4) elements, using channel as an index: lan743x_ptp_io_event_clock_get(..., u8 channel,...) { ... /* Update Local timestamp */ extts = &ptp->extts[channel]; extts->ts.tv_sec = sec; ... } To avoid an out-of-bounds write and utilize all the supported GPIO inputs, set LAN743X_PTP_N_EXTTS to 8. Detected using the static analysis tool - Svace.
osv:CVE-2025-38183
Kernel
Fixed versions: 6.1.142, 6.6.95, 6.12.35, 6.15.4
Complete source record
{
"id": "bdbbd9b12f32fb5dd06ea950bb4cf4721444451994198ab835f95d1b558a3b1b",
"url": "https://osv.dev/vulnerability/CVE-2025-38183",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "net: lan743x: fix potential out-of-bounds write in lan743x_ptp_io_event_clock_get()",
"summary": "In the Linux kernel, the following vulnerability has been resolved: net: lan743x: fix potential out-of-bounds write in lan743x_ptp_io_event_clock_get() Before calling lan743x_ptp_io_event_clock_get(), the 'channel' value is checked against the maximum value of PCI11X1X_PTP_IO_MAX_CHANNELS(8). This seems correct and aligns with the PTP interrupt status register (PTP_INT_STS) specifications. However, lan743x_ptp_io_event_clock_get() writes to ptp->extts[] with only LAN743X_PTP_N_EXTTS(4) elements, using channel as an index: lan743x_ptp_io_event_clock_get(..., u8 channel,...) { ... /* Update Local timestamp */ extts = &ptp->extts[channel]; extts->ts.tv_sec = sec; ... } To avoid an out-of-bounds write and utilize all the supported GPIO inputs, set LAN743X_PTP_N_EXTTS to 8. Detected using the static analysis tool - Svace.",
"evidence": "osv:CVE-2025-38183",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.1.142",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.95",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.35",
"evidence": "/affected/1/ranges"
},
{
"value": "6.15.4",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2025-38183",
"aliases": [
"CVE-2025-38183"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "60942c397af6094c04406b77982314dfe69ef3c4"
},
{
"fixed": "e8d48201a132f4aab31351c19a802c5a5ae820fa"
},
{
"fixed": "66bba1fd5bad548c03f7e42669a59f3f4d8211cc"
},
{
"fixed": "41017bd66c533f7af912c58273c7dfd5de0065d4"
},
{
"fixed": "4da0d23516857230b8e9b3022e25422ee2e2ba80"
},
{
"fixed": "e353b0854d3a1a31cb061df8d022fbfea53a0f24"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38183.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.18.0"
},
{
"fixed": "6.1.142"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.95"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.35"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.15.4"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38183.json"
}
}
],
"modified": "2026-10-28T02:30:40.457395715Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/41017bd66c533f7af912c58273c7dfd5de0065d4",
"https://git.kernel.org/stable/c/4da0d23516857230b8e9b3022e25422ee2e2ba80",
"https://git.kernel.org/stable/c/66bba1fd5bad548c03f7e42669a59f3f4d8211cc",
"https://git.kernel.org/stable/c/e353b0854d3a1a31cb061df8d022fbfea53a0f24",
"https://git.kernel.org/stable/c/e8d48201a132f4aab31351c19a802c5a5ae820fa",
"https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38183.json",
"https://nvd.nist.gov/vuln/detail/CVE-2025-38183",
"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-38183.json"
}
},
"related_cves": [
{
"value": "CVE-2025-38183",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 507842,
"published_at": "2025-07-04T13:37:10.253+00:00"
}