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

{
  "id": "7564ec6250b507b12c7dd470a774e619259ecc5c201c791ec0a4a8ad78e0c793",
  "url": "https://osv.dev/vulnerability/CVE-2026-53231",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "net: phy: don't try to setup PHY-driven SFP cages when using genphy",
    "summary": "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.",
    "evidence": "osv:CVE-2026-53231",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "7.0.13",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2026-53231",
      "aliases": [
        "CVE-2026-53231"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "bad869b5e41a08424ff130fd6bb41b854be70095"
                },
                {
                  "fixed": "ef8d739eee6f85303cbecebc01eb72f063de74e0"
                },
                {
                  "fixed": "5a0082ec20a05ef2378410323a5089a8f1786f4a"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53231.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "7.0.0"
                },
                {
                  "fixed": "7.0.13"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53231.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:26.681622670Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/5a0082ec20a05ef2378410323a5089a8f1786f4a",
        "https://git.kernel.org/stable/c/ef8d739eee6f85303cbecebc01eb72f063de74e0",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53231.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-53231",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53231.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-53231",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 493179,
  "published_at": "2026-06-25T08:39:29.871+00:00"
}