{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-53232","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2026-06-09T07:44:35.393Z","datePublished":"2026-06-25T08:39:30.527Z","dateUpdated":"2026-08-05T12:34:23.514Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-08-05T12:34:23.514Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: clean the sfp upstream if phy probing fails\n\nSashiko reported that we don't call sfp_bus_del_upstream() in the probe\nfailure path, so let's add it, otherwise the sfp-bus is left with a\ndangling 'upstream' field, that may be used later on during SFP events.\n\nThis issue existed before the generic phylib sfp support, back when\ndrivers were calling phy_sfp_probe themselves."}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","baseScore":8.8,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:A - The stale upstream pointer is dereferenced from SFP cage events such as module presence and LOS/link changes, which can be driven by a directly connected SFP link partner. It is not reachable through ordinary routed network packets or an unprivileged syscall path.\nAC:L - Once an affected PHY/SFP configuration has hit the failed-probe state, later SFP events reliably call the stale upstream callbacks. There is no attacker-won race or complex timing requirement in the event path.\nPR:N - An adjacent physical/link-layer attacker does not need kernel privileges or authentication to trigger SFP signal events. No CAP_NET_ADMIN or user-namespace route is required for that trigger path.\nUI:N - After the system is in the vulnerable failed-probe state, exploitation is triggered by SFP events without a victim user performing an action. The attacker can induce the relevant link/module event directly.\nS:U - The affected code and resulting impact are within the Linux kernel networking/PHY security authority. There is no VM, IOMMU, or separate-scope boundary crossing.\nC:H - The bug leaves a dangling `phy_device` upstream pointer that later SFP callbacks dereference, creating a kernel use-after-free style condition. Kernel UAF conditions are treated as capable of exposing arbitrary kernel memory.\nI:H - The stale pointer callbacks read and write fields through the freed or invalid `phy_device` and may reach attacker-influenced object contents after reuse. Kernel UAF memory corruption is treated as potentially enabling arbitrary write or code execution.\nA:H - Even without full exploitation, dereferencing the dangling upstream pointer during SFP events can crash or oops the kernel. Kernel crashes are high availability impact."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/net/phy/phy_device.c"],"versions":[{"version":"298e54fa810e027f1b0800d789eb862592721f08","lessThan":"12fb84dc4dc8eb47ebe2b27f7de6255a4a205e1b","status":"affected","versionType":"git"},{"version":"298e54fa810e027f1b0800d789eb862592721f08","lessThan":"9326b654f90a09eadeb796c82801a5609d57f0c8","status":"affected","versionType":"git"},{"version":"298e54fa810e027f1b0800d789eb862592721f08","lessThan":"3a254779c169954fe23328a1db51f67be374f913","status":"affected","versionType":"git"},{"version":"298e54fa810e027f1b0800d789eb862592721f08","lessThan":"0b27701ce93161d7bbf4b25fa20ca59963b0e20c","status":"affected","versionType":"git"},{"version":"298e54fa810e027f1b0800d789eb862592721f08","lessThan":"48774e87bbaa0056819d4b52301e4692e50e3252","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/net/phy/phy_device.c"],"versions":[{"version":"5.5","status":"affected"},{"version":"0","lessThan":"5.5","status":"unaffected","versionType":"semver"},{"version":"6.6.143","lessThanOrEqual":"6.6.*","status":"unaffected","versionType":"semver"},{"version":"6.12.94","lessThanOrEqual":"6.12.*","status":"unaffected","versionType":"semver"},{"version":"6.18.36","lessThanOrEqual":"6.18.*","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"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.5","versionEndExcluding":"6.6.143"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.5","versionEndExcluding":"6.12.94"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.5","versionEndExcluding":"6.18.36"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.5","versionEndExcluding":"7.0.13"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.5","versionEndExcluding":"7.1"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/12fb84dc4dc8eb47ebe2b27f7de6255a4a205e1b"},{"url":"https://git.kernel.org/stable/c/9326b654f90a09eadeb796c82801a5609d57f0c8"},{"url":"https://git.kernel.org/stable/c/3a254779c169954fe23328a1db51f67be374f913"},{"url":"https://git.kernel.org/stable/c/0b27701ce93161d7bbf4b25fa20ca59963b0e20c"},{"url":"https://git.kernel.org/stable/c/48774e87bbaa0056819d4b52301e4692e50e3252"}],"title":"net: phy: clean the sfp upstream if phy probing fails","x_generator":{"engine":"bippy-1.2.0"}}}}