{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-53231","id":"CVE-2026-53231","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\nT","descriptionLong":"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.","published":"2026-06-25T08:39:29.871Z","updated":"2026-10-28T02:30:26.681622670Z","reserved":"2026-06-09T07:44:35.393Z","status":"Analyzed","rejected":false,"assigner":"Linux","metric":{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","rating":"medium","source":"NVD"},"metrics":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","rating":"medium","source":"NVD"}],"rating":"medium","products":["Linux"],"affectedProducts":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"bad869b5e41a08424ff130fd6bb41b854be70095","lessThan":"ef8d739eee6f85303cbecebc01eb72f063de74e0","status":"affected","versionType":"git"},{"version":"bad869b5e41a08424ff130fd6bb41b854be70095","lessThan":"5a0082ec20a05ef2378410323a5089a8f1786f4a","status":"affected","versionType":"git"}],"platforms":[]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"7.0","status":"affected"},{"version":"0","lessThan":"7.0","status":"unaffected","versionType":"semver"},{"version":"7.0.13","lessThanOrEqual":"7.0.*","status":"unaffected","versionType":"semver"},{"version":"7.1","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}],"platforms":[]}],"packages":[],"cwes":["CWE-667"],"aliases":[],"references":[{"url":"https://git.kernel.org/stable/c/ef8d739eee6f85303cbecebc01eb72f063de74e0","tags":["Patch","web"]},{"url":"https://git.kernel.org/stable/c/5a0082ec20a05ef2378410323a5089a8f1786f4a","tags":["Patch","web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53231.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53231","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","tags":["package"]}],"patchReferenced":true,"fixAvailable":true,"exploitReferenced":false,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":null,"epss":0.00111,"epssPercentile":0.01335,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-53231","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53231","ok":true,"note":"Analyzed"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-53231","ok":true,"note":"0 packages"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-53231","ok":true,"note":"scored 2026-11-18"}],"aiTitle":false,"tech":[],"critical":[],"attention":null}