CVE-2025-38183 Details
Description
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.
A potential out-of-bounds write vulnerability has been identified in the Linux kernel's handling of Precision Time Protocol (PTP) IO events for the LAN743X network driver. The issue arises in the function 'lan743x_ptp_io_event_clock_get()', where the 'channel' index is not properly validated against the actual number of available channels. Although the 'channel' value is initially checked to ensure it does not exceed the maximum number of PTP IO channels, the subsequent write operation to the PTP external timestamp array does not account for the possibility of exceeding the array's bounds. This vulnerability could lead to memory corruption by allowing writes beyond the allocated array size.
To address this vulnerability, the 'LAN743X_PTP_N_EXTTS' constant should be set to 8, ensuring that all supported channels are properly accounted for in the PTP IO event handling.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/41017bd66c533f7af912c58273c7dfd5de0065d4 | kernel.org | Patch |
| https://git.kernel.org/stable/c/4da0d23516857230b8e9b3022e25422ee2e2ba80 | kernel.org | Patch |
| https://git.kernel.org/stable/c/66bba1fd5bad548c03f7e42669a59f3f4d8211cc | kernel.org | Patch |
| https://git.kernel.org/stable/c/e353b0854d3a1a31cb061df8d022fbfea53a0f24 | kernel.org | Patch |
| https://git.kernel.org/stable/c/e8d48201a132f4aab31351c19a802c5a5ae820fa | kernel.org | Patch |
| https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html | CVE | Third Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-787 | Out-of-bounds Write | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.18, < 6.1.142 >= 6.2, < 6.6.95 >= 6.7, < 6.12.35 >= 6.13, < 6.15.4 6.16 rc1 6.16 rc2 |
CPE
Remediation
| |
| debian debian linux | 11.0 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 18, 2025 | Initial Analysis | [email protected] |
| Nov 3, 2025 | CVE Modified | CVE |
| Jul 4, 2025 | New CVE Received | kernel.org |