CVE-2025-71196

UnknownEPSS 0.17%

Last modified

CVE-2025-71196 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.17% chance of exploitation in the next 30 days.

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 >=.

Metrics

EPSS Probability
0.17%

7.0th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 94c358da3a0545205c6c6a50ae26141f1c73acfa, < a9eec890879731c280697fdf1c50699e905b2fa7; >= 94c358da3a0545205c6c6a50ae26141f1c73acfa, < fb9d513cdf1614bf0f0e785816afb1faae3f81af; >= 94c358da3a0545205c6c6a50ae26141f1c73acfa, < c06f13876cbad702582cd67fc77356e5524d02cd; >= 94c358da3a0545205c6c6a50ae26141f1c73acfa, < 76b870fdaad82171a24b8aacffe5e4d9e0d2ee2c; >= 94c358da3a0545205c6c6a50ae26141f1c73acfa, < b91c9f6bfb04e430adeeac7e7ebc9d80f9d72bad; >= 94c358da3a0545205c6c6a50ae26141f1c73acfa, < 7c27eaf183563b86d815ff6e9cca0210b4cfa051; >= 94c358da3a0545205c6c6a50ae26141f1c73acfa, < cabd25b57216ddc132efbcc31f972baa03aad15a
LinuxLinux4.17

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is CVE-2025-71196?
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 >=.
How severe is CVE-2025-71196?
Severity scoring for CVE-2025-71196 is pending analysis. The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2025-71196?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2025

Are you affected by CVE-2025-71196?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST