Answer in brief
CVE-2025-38149 records a Medium severity (CVSS 5.5) vulnerability in net: phy: clear phydev->devlink when the link is deleted. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=bc66fa87d4fda9053a8145e5718fc278c2b88253 <363fdf2777423ad346d781f09548cca14877f729 || >=bc66fa87d4fda9053a8145e5718fc278c2b88253 <ddc654e89ace723b78c34911c65243accbc9b75c || >=bc66fa87d4fda9053a8145e5718fc278c2b88253 <034bc4a2a72dea2cfcaf24c6bae03c38ad5a0b87 || >=bc66fa87d4fda9053a8145e5718fc278c2b88253 <0795b05a59b1371b18ffbf09d385296b12e9f5d5 | 363fdf2777423ad346d781f09548cca14877f729, ddc654e89ace723b78c34911c65243accbc9b75c, 034bc4a2a72dea2cfcaf24c6bae03c38ad5a0b87, 0795b05a59b1371b18ffbf09d385296b12e9f5d5 |
| Linux/Linuxgeneric | 6.2 | Not reported |
Published upstream
Jul 3, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.