Skip to content
Noroxi
CVE-2025-71196· NVD / CVE Program· CNA Linux

phy: stm32-usphyc: Fix off by one in probe()

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
  • Fixed version: Linux Linux 76b870fdaad82171a24b8aacffe5e4d9e0d2ee2c, 7c27eaf183563b86d815ff6e9cca0210b4cfa051, a9eec890879731c280697fdf1c50699e905b2fa7.

Low priority for now. Upgrade to Linux Linux 76b870fdaad82171a24b8aacffe5e4d9e0d2ee2c, 7c27eaf183563b86d815ff6e9cca0210b4cfa051, a9eec890879731c280697fdf1c50699e905b2fa7 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

—No exploit Fix available
Published
Feb 4, 2026
Updated
Jun 17, 2026
EPSS
0.2% · 9th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-71196

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.17affected
    • 94c358da3a0545205c6c6a50ae26141f1c73acfa and later · before a9eec890879731c280697fdf1c50699e905b2fa7affected · git
    • 94c358da3a0545205c6c6a50ae26141f1c73acfa and later · before fb9d513cdf1614bf0f0e785816afb1faae3f81afaffected · git
    • 94c358da3a0545205c6c6a50ae26141f1c73acfa and later · before c06f13876cbad702582cd67fc77356e5524d02cdaffected · git
    • 94c358da3a0545205c6c6a50ae26141f1c73acfa and later · before 76b870fdaad82171a24b8aacffe5e4d9e0d2ee2caffected · git
    • 94c358da3a0545205c6c6a50ae26141f1c73acfa and later · before b91c9f6bfb04e430adeeac7e7ebc9d80f9d72badaffected · git
    • 94c358da3a0545205c6c6a50ae26141f1c73acfa and later · before 7c27eaf183563b86d815ff6e9cca0210b4cfa051affected · git
    • 94c358da3a0545205c6c6a50ae26141f1c73acfa and later · before cabd25b57216ddc132efbcc31f972baa03aad15aaffected · git
    • before 4.17not affected · semver
    • 5.10.249 and later · up to and including 5.10.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.162-16.1.162-1
Debian:13linuxbefore 6.12.69-16.12.69-1
Debian:14linuxbefore 6.18.8-16.18.8-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-71193Feb 4, 2026 · phy: qcom-qusb2: Fix NULL pointer dereference on early suspend
    0Monitor
  • ← EarlierCVE-2025-71195Feb 4, 2026 · dmaengine: xilinx: xdma: Fix regmap max_register
    0Monitor
  • Later →CVE-2025-71198Feb 4, 2026 · iio: imu: st_lsm6dsx: fix iio_chan_spec for sensors without event detection
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux76b870fdaad82171a24b8aacffe5e4d9e0d2ee2cVendor (CNA)
Linux Linux7c27eaf183563b86d815ff6e9cca0210b4cfa051Vendor (CNA)
Linux Linuxa9eec890879731c280697fdf1c50699e905b2fa7Vendor (CNA)
Linux Linuxb91c9f6bfb04e430adeeac7e7ebc9d80f9d72badVendor (CNA)
Linux Linuxc06f13876cbad702582cd67fc77356e5524d02cdVendor (CNA)
Linux Linuxcabd25b57216ddc132efbcc31f972baa03aad15aVendor (CNA)
Linux Linuxfb9d513cdf1614bf0f0e785816afb1faae3f81afVendor (CNA)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records