VulnerabilityPublished 3 Jul 2025Updated 5 Nov 2026

CVE-2025-38149: Linux kernel · net: phy: clear phydev->devlink when the link is deleted

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in ddc654e89ace723b78c34911c65243accbc9b75c : update Linux kernel when convenient.

Data as of 5 Nov 2026, 23:23 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

EPSS

0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch

Available – fixed in ddc654e89ace723b78c34911c65243accbc9b75c, 0795b05a59b1371b18ffbf09d385296b12e9f5d5, 363fdf2777423ad346d781f09548cca14877f729 +1

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to ddc654e89ace723b78c34911c65243accbc9b75c, 0795b05a59b1371b18ffbf09d385296b12e9f5d5, 363fdf2777423ad346d781f09548cca14877f729 or 034bc4a2a72dea2cfcaf24c6bae03c38ad5a0b87.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ bc66fa87d4fda9053a8145e5718fc278c2b88253, < ddc654e89ace723b78c34911c65243accbc9b75c	Fixed in ddc654e89ace723b78c34911c65243accbc9b75c
LinuxLinux	Affected ≥ bc66fa87d4fda9053a8145e5718fc278c2b88253, < 0795b05a59b1371b18ffbf09d385296b12e9f5d5	Fixed in 0795b05a59b1371b18ffbf09d385296b12e9f5d5
LinuxLinux	Affected ≥ bc66fa87d4fda9053a8145e5718fc278c2b88253, < 363fdf2777423ad346d781f09548cca14877f729	Fixed in 363fdf2777423ad346d781f09548cca14877f729
LinuxLinux	Affected ≥ bc66fa87d4fda9053a8145e5718fc278c2b88253, < 034bc4a2a72dea2cfcaf24c6bae03c38ad5a0b87	Fixed in 034bc4a2a72dea2cfcaf24c6bae03c38ad5a0b87
LinuxLinux	Affected =6.2	Fixed in–

Description

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.

References

Community reviews

Loading reviews…