Executive Summary



This vulnerability is currently undergoing analysis and not all information is available. Please check back soon to view the completed vulnerability summary
Informations
Name CVE-2025-38183 First vendor Publication 2025-07-04
Vendor Cve Last vendor Modification 2025-07-04

Security-Database Scoring CVSS v3

Cvss vector : N/A
Overall CVSS Score NA
Base Score NA Environmental Score NA
impact SubScore NA Temporal Score NA
Exploitabality Sub Score NA
 
Calculate full CVSS 3.0 Vectors scores

Security-Database Scoring CVSS v2

Cvss vector :
Cvss Base Score N/A Attack Range N/A
Cvss Impact Score N/A Attack Complexity N/A
Cvss Expoit Score N/A Authentication N/A
Calculate full CVSS 2.0 Vectors scores

Detail

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.

Original Source

Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-38183

Sources (Detail)

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
Source Url

Alert History

If you want to see full details history, please login or register.
0
Date Informations
2025-07-04 21:20:36
  • First insertion