{"api_version":"1","generated_at":"2026-06-26T18:17:02+00:00","cve":"CVE-2026-53231","urls":{"html":"https://cve.report/CVE-2026-53231","api":"https://cve.report/api/cve/CVE-2026-53231.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-53231","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-53231"},"summary":{"title":"net: phy: don't try to setup PHY-driven SFP cages when using genphy","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: don't try to setup PHY-driven SFP cages when using genphy\n\nWe don't have support for PHY-driver SFP cages with the genphy code.\n\nOn top of that, it was found by sashiko that running\nsfp_bus_add_upstream() for genphy deadlocks, as for genphy the PHY\nprobing runs under RTNL, which isn't the case for non-genphy drivers.\n\nThis problem was reproduced, and does lead to a deadlock on RTNL.\n\nBefore the blamed commit, the phy_sfp_probe() call was made by\nindividual PHY drivers, so there was no way to get to the SFP probing\npath when using genphy.\n\nLet's therefore only run phy_sfp_probe when not using genphy.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-06-25 09:16:41","updated_at":"2026-06-25 09:16:41"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/5a0082ec20a05ef2378410323a5089a8f1786f4a","name":"https://git.kernel.org/stable/c/5a0082ec20a05ef2378410323a5089a8f1786f4a","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/ef8d739eee6f85303cbecebc01eb72f063de74e0","name":"https://git.kernel.org/stable/c/ef8d739eee6f85303cbecebc01eb72f063de74e0","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-53231","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53231","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected bad869b5e41a08424ff130fd6bb41b854be70095 ef8d739eee6f85303cbecebc01eb72f063de74e0 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected bad869b5e41a08424ff130fd6bb41b854be70095 5a0082ec20a05ef2378410323a5089a8f1786f4a git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7.0","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0.13 7.0.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"53231","cve":"CVE-2026-53231","epss":"0.001620000","percentile":"0.057700000","score_date":"2026-06-25","updated_at":"2026-06-26 00:06:14"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/net/phy/phy_device.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"ef8d739eee6f85303cbecebc01eb72f063de74e0","status":"affected","version":"bad869b5e41a08424ff130fd6bb41b854be70095","versionType":"git"},{"lessThan":"5a0082ec20a05ef2378410323a5089a8f1786f4a","status":"affected","version":"bad869b5e41a08424ff130fd6bb41b854be70095","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/net/phy/phy_device.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"7.0"},{"lessThan":"7.0","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.0.*","status":"unaffected","version":"7.0.13","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0.13","versionStartIncluding":"7.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1","versionStartIncluding":"7.0","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: don't try to setup PHY-driven SFP cages when using genphy\n\nWe don't have support for PHY-driver SFP cages with the genphy code.\n\nOn top of that, it was found by sashiko that running\nsfp_bus_add_upstream() for genphy deadlocks, as for genphy the PHY\nprobing runs under RTNL, which isn't the case for non-genphy drivers.\n\nThis problem was reproduced, and does lead to a deadlock on RTNL.\n\nBefore the blamed commit, the phy_sfp_probe() call was made by\nindividual PHY drivers, so there was no way to get to the SFP probing\npath when using genphy.\n\nLet's therefore only run phy_sfp_probe when not using genphy."}],"providerMetadata":{"dateUpdated":"2026-06-25T08:39:29.871Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/ef8d739eee6f85303cbecebc01eb72f063de74e0"},{"url":"https://git.kernel.org/stable/c/5a0082ec20a05ef2378410323a5089a8f1786f4a"}],"title":"net: phy: don't try to setup PHY-driven SFP cages when using genphy","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-53231","datePublished":"2026-06-25T08:39:29.871Z","dateReserved":"2026-06-09T07:44:35.393Z","dateUpdated":"2026-06-25T08:39:29.871Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-06-25 09:16:41","lastModifiedDate":"2026-06-25 09:16:41","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"53231","Ordinal":"1","Title":"net: phy: don't try to setup PHY-driven SFP cages when using gen","CVE":"CVE-2026-53231","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"53231","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: don't try to setup PHY-driven SFP cages when using genphy\n\nWe don't have support for PHY-driver SFP cages with the genphy code.\n\nOn top of that, it was found by sashiko that running\nsfp_bus_add_upstream() for genphy deadlocks, as for genphy the PHY\nprobing runs under RTNL, which isn't the case for non-genphy drivers.\n\nThis problem was reproduced, and does lead to a deadlock on RTNL.\n\nBefore the blamed commit, the phy_sfp_probe() call was made by\nindividual PHY drivers, so there was no way to get to the SFP probing\npath when using genphy.\n\nLet's therefore only run phy_sfp_probe when not using genphy.","Type":"Description","Title":"net: phy: don't try to setup PHY-driven SFP cages when using gen"}]}}}