CVE-2025-38149
net: phy: clear phydev->devlink when the link is deleted
In the Linux kernel, the following vulnerability has been resolved: net: phy: clear phydev->devlink when the link is deleted There is a potential crash issue when disabling and re-enabling the network port. When disabling the network port, phy_detach() calls device_link_del() to remove the device link, but it does not clear phydev->devlink, so phydev->devlink is not a NULL pointer. Then the network port is re-enabled, but if phy_attach_direct() fails before calling device_link_add(), the code jumps to the "error" label and calls phy_detach(). Since phydev->devlink retains the old value from the previous attach/detach cycle, device_link_del() uses the old value, which accesses a NULL pointer and causes a crash. The simplified crash log is as follows. [ 24.702421] Call trace: [ 24.704856] device_link_put_kref+0x20/0x120 [ 24.709124] device_link_del+0x30/0x48 [ 24.712864] phy_detach+0x24/0x168 [ 24.716261] phy_attach_direct+0x168/0x3a4 [ 24.720352] phylink_fwnode_phy_connect+0xc8/0x14c [ 24.725140] phylink_of_phy_connect+0x1c/0x34 Therefore, phydev->devlink needs to be cleared when the device link is deleted.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ bc66fa87d4fda9053a8145e5718fc278c2b88253; < 363fdf2777423ad346d781f09548cca14877f729 (affected, git) ≥ bc66fa87d4fda9053a8145e5718fc278c2b88253; < ddc654e89ace723b78c34911c65243accbc9b75c (affected, git) ≥ bc66fa87d4fda9053a8145e5718fc278c2b88253; < 034bc4a2a72dea2cfcaf24c6bae03c38ad5a0b87 (affected, git) ≥ bc66fa87d4fda9053a8145e5718fc278c2b88253; < 0795b05a59b1371b18ffbf09d385296b12e9f5d5 (affected, git) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
6.2 (affected) ≥ 0; < 6.2 (unaffected, semver) ≥ 6.6.94; ≤ 6.6.* (unaffected, semver) ≥ 6.12.34; ≤ 6.12.* (unaffected, semver) ≥ 6.15.3; ≤ 6.15.* (unaffected, semver) ≥ 6.16; ≤ * (unaffected, original_commit_for_fix) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
No CVSS assessment reported. An unscored record is not a low-severity determination.
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/363fdf2777423ad346d781f09548cca14877f729CNA: Linux
- https://git.kernel.org/stable/c/ddc654e89ace723b78c34911c65243accbc9b75cCNA: Linux
- https://git.kernel.org/stable/c/034bc4a2a72dea2cfcaf24c6bae03c38ad5a0b87CNA: Linux
- https://git.kernel.org/stable/c/0795b05a59b1371b18ffbf09d385296b12e9f5d5CNA: Linux
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.