{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-71196 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-71196 is a vulnerability in Linux, published on 4 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-71196 and fix it if it is affected.\n\nWhat it is: CVE-2025-71196 is a vulnerability in Linux, published on 4 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-71196 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-71196/ (Markdown: https://insights.sbomify.com/CVE-2025-71196/index.md)","id":"CVE-2025-71196","markdown":"https://insights.sbomify.com/CVE-2025-71196/index.md","name":"CVE-2025-71196","record":{"aliases":["BELL-CVE-2025-71196","DEBIAN-CVE-2025-71196","GHSA-26mr-48wg-9jv2","ROOT-OS-UBUNTU-2204-CVE-2025-71196","ROOT-OS-UBUNTU-2404-CVE-2025-71196","UBUNTU-CVE-2025-71196"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"An off-by-one error in the STM32 USPHyC driver probe function can lead to an out-of-bounds array access, potentially causing a system crash.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nphy: stm32-usphyc: Fix off by one in probe()\n\nThe \"index\" variable is used as an index into the usbphyc-\u003ephys[] array\nwhich has usbphyc-\u003enphys elements.  So if it is equal to usbphyc-\u003enphys\nthen it is one element out of bounds.  The \"index\" comes from the\ndevice tree so it's data that we trust and it's unlikely to be wrong,\nhowever it's obviously still worth fixing the bug.  Change the \u003e to \u003e=.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"phy: stm32-usphyc: Fix off by one in probe()","id":"CVE-2025-71196","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"w1: therm: Fix off-by-one buffer overflow in alarms_store","id":"CVE-2025-71197"},"packages":[],"prev":{"headline":"dmaengine: xilinx: xdma: Fix regmap max_register","id":"CVE-2025-71195"},"products":["Linux"],"published":"2026-02-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"An off-by-one error in the STM32 USPHyC driver probe function can lead to an out-of-bounds array access, potentially causing a system crash.","url":"https://insights.sbomify.com/CVE-2025-71196/"}