CVE-2025-71196
Unknown Unknown - Not Provided

Off-by-One Vulnerability in Linux stm32-usphyc USB PHY Probe

Publication date: 2026-02-04

Last updated on: 2026-02-06

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: phy: stm32-usphyc: Fix off by one in probe() The "index" variable is used as an index into the usbphyc->phys[] array which has usbphyc->nphys elements. So if it is equal to usbphyc->nphys then it is one element out of bounds. The "index" comes from the device tree so it's data that we trust and it's unlikely to be wrong, however it's obviously still worth fixing the bug. Change the > to >=.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-02-04
Last Modified
2026-02-06
Generated
2026-07-06
AI Q&A
2026-02-04
EPSS Evaluated
2026-07-05
NVD
CVE-2025-71196

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is an off-by-one error in the Linux kernel's stm32-usphyc driver during the probe() function.

Specifically, the 'index' variable is used to access elements in the usbphyc->phys[] array, which has usbphyc->nphys elements.

If 'index' equals usbphyc->nphys, it goes one element out of bounds, which is an invalid access.

The 'index' value comes from the device tree, which is generally trusted, but the bug was fixed by changing the condition from '>' to '>=' to prevent this out-of-bounds access.

Impact Analysis

I don't know

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

I don't know

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-71196. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart