{"id":"CVE-2025-38149","title":"net: phy: clear phydev->devlink when the link is deleted","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: clear phydev->devlink when the link is deleted\n\nThere is a potential crash issue when disabling and re-enabling the\nnetwork port. When disabling the network p…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= bc66fa87d4fda9053a8145e5718fc278c2b88253 < 363fdf2777423ad346d781f09548cca14877f729","Linux >= bc66fa87d4fda9053a8145e5718fc278c2b88253 < ddc654e89ace723b78c34911c65243accbc9b75c","Linux >= bc66fa87d4fda9053a8145e5718fc278c2b88253 < 034bc4a2a72dea2cfcaf24c6bae03c38ad5a0b87","Linux >= bc66fa87d4fda9053a8145e5718fc278c2b88253 < 0795b05a59b1371b18ffbf09d385296b12e9f5d5","Linux 6.2"],"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial","timestamp":"2026-11-05T20:50:35.495712Z"},"published":"2025-07-03","updated":"2026-11-05","sourceUpdated":"2026-11-05T20:52:17.920Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2025-38149","references":[{"url":"https://git.kernel.org/stable/c/363fdf2777423ad346d781f09548cca14877f729"},{"url":"https://git.kernel.org/stable/c/ddc654e89ace723b78c34911c65243accbc9b75c"},{"url":"https://git.kernel.org/stable/c/034bc4a2a72dea2cfcaf24c6bae03c38ad5a0b87"},{"url":"https://git.kernel.org/stable/c/0795b05a59b1371b18ffbf09d385296b12e9f5d5"}],"tags":["cve.org"],"epss":0.00181,"epssPercentile":0.07732,"ingestedAt":"2026-11-05T22:38:31.925Z","slug":"CVE-2025-38149","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: clear phydev->devlink when the link is deleted\n\nThere is a potential crash issue when disabling and re-enabling the\nnetwork port. When disabling the network port, phy_detach() calls\ndevice_link_del() to remove the device link, but it does not clear\nphydev->devlink, so phydev->devlink is not a NULL pointer. Then the\nnetwork port is re-enabled, but if phy_attach_direct() fails before\ncalling device_link_add(), the code jumps to the \"error\" label and\ncalls phy_detach(). Since phydev->devlink retains the old value from\nthe previous attach/detach cycle, device_link_del() uses the old value,\nwhich accesses a NULL pointer and causes a crash. The simplified crash\nlog is as follows.\n\n[   24.702421] Call trace:\n[   24.704856]  device_link_put_kref+0x20/0x120\n[   24.709124]  device_link_del+0x30/0x48\n[   24.712864]  phy_detach+0x24/0x168\n[   24.716261]  phy_attach_direct+0x168/0x3a4\n[   24.720352]  phylink_fwnode_phy_connect+0xc8/0x14c\n[   24.725140]  phylink_of_phy_connect+0x1c/0x34\n\nTherefore, phydev->devlink needs to be cleared when the device link is\ndeleted.\n\n## Affected\n\n- `Linux >= bc66fa87d4fda9053a8145e5718fc278c2b88253 < 363fdf2777423ad346d781f09548cca14877f729`\n- `Linux >= bc66fa87d4fda9053a8145e5718fc278c2b88253 < ddc654e89ace723b78c34911c65243accbc9b75c`\n- `Linux >= bc66fa87d4fda9053a8145e5718fc278c2b88253 < 034bc4a2a72dea2cfcaf24c6bae03c38ad5a0b87`\n- `Linux >= bc66fa87d4fda9053a8145e5718fc278c2b88253 < 0795b05a59b1371b18ffbf09d385296b12e9f5d5`\n- `Linux 6.2`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}