CVE-2025-38183 [High] | Out-of-bounds Write in Linux Kernel

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.06%	0.15%	+0.09%
2	2026-04-30	0.02%	0.06%	+0.04%
3	2025-12-19	—	0.02%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.06%

0.15%

+0.09%

2026-04-30

0.02%

0.06%

+0.04%

2025-12-19

—

0.02%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.9

[email protected]

OS Trackers for CVE-2025-38183

vendor	priority	summary	link
`debian`	unimportant	CVE-2025-38183 unimportant priority: Debian including 2 source packages (linux, linux-6.1), 6 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 6.	https://security-tracker.debian.org/tracker/CVE-2025-38183
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2025-38183
`suse`	high	CVE-2025-38183 severity important: SUSE including 433 source package names (2.1.3-6.67:kernel-default-base-6.4.0-32.1.21.10, 2.1.3-7.44:kernel-default-6.4.0-32.1, …), 910 product×package rows across 186 product lines (Container suse/sl-micro/6.0/base-os-container, Container suse/sl-micro/6.0/kvm-os-container, … (186 product lines)): Fixed 476, Known Affected 231, Known Not Affected 203.	https://www.suse.com/security/cve/CVE-2025-38183/
`ubuntu`	medium	CVE-2025-38183 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, ignored 164, released 138, not-affected 99, needed 2, needs-triage 2, pending 1.	https://ubuntu.com/security/CVE-2025-38183

Affected software / configurations for CVE-2025-38183

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 5.18, < 6.1.142	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.2, < 6.6.95	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.7, < 6.12.35	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.13, < 6.15.4	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	6.16	cpe:2.3:o:linux:linux_kernel:6.16:rc1::::::
linux	linux_kernel	6.16	cpe:2.3:o:linux:linux_kernel:6.16:rc2::::::
debian	debian_linux	11.0	cpe:2.3:o:debian:debian_linux:11.0:::::::*

References for CVE-2025-38183

URL	Tags
https://git.kernel.org/stable/c/41017bd66c533f7af912c58273c7dfd5de0065d4	Patch
https://git.kernel.org/stable/c/4da0d23516857230b8e9b3022e25422ee2e2ba80	Patch
https://git.kernel.org/stable/c/66bba1fd5bad548c03f7e42669a59f3f4d8211cc	Patch
https://git.kernel.org/stable/c/e353b0854d3a1a31cb061df8d022fbfea53a0f24	Patch
https://git.kernel.org/stable/c/e8d48201a132f4aab31351c19a802c5a5ae820fa	Patch
https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html	Third Party Advisory

URL

CVE-2025-38183 | net: lan743x: fix potential out-of-bounds write in lan743x_ptp_io_event_clock_get()

Exploit prediction scoring system (EPSS) score for CVE-2025-38183

Common vulnerability scoring system (CVSS) metrics for CVE-2025-38183

Weakness enumeration for CVE-2025-38183

OS Trackers for CVE-2025-38183

Affected software / configurations for CVE-2025-38183

References for CVE-2025-38183