7

CVE-2025-39905: net: phylink: add lock for serializing concurrent pl->phydev writes with resolver

Modified
AliasesUBUNTU-CVE-2025-39905DEBIAN-CVE-2025-39905CGA-23f2-5q2w-m7jf
Published 01-10-2025Last modified 11-05-2026

Vulnerability summary

CVE-2025-39905 is a high (CVSS 7.0) vulnerability in linux. EPSS estimates a 0.11% chance of exploitation in the next 30 days, higher than 1.3% of scored vulnerabilities.

Priority
Routine

Not severe (CVSS 7, local access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
7.0/10
010
High · v3.1 (CVE.org)
EPSS score
0.11%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 1 · Related 1

Timeline

  1. 01-10-2025
    PublishedVulnerability first disclosed.
  2. 11-05-2026
    Last modifiedVulnerability information updated.

Description

In the Linux kernel, the following vulnerability has been resolved: net: phylink: add lock for serializing concurrent pl->phydev writes with resolver Currently phylink_resolve() protects itself against concurrent phylink_bringup_phy() or phylink_disconnect_phy() calls which modify pl->phydev by relying on pl->state_mutex. The problem is that in phylink_resolve(), pl->state_mutex is in a lock inversion state with pl->phydev->lock. So pl->phydev->lock needs to be acquired prior to pl->state_mutex. But that requires dereferencing pl->phydev in the first place, and without pl->state_mutex, that is racy. Hence the reason for the extra lock. Currently it is redundant, but it will serve a functional purpose once mutex_lock(&phy->lock) will be moved outside of the mutex_lock(&pl->state_mutex) section. Another alternative considered would have been to let phylink_resolve() acquire the rtnl_mutex, which is also held when phylink_bringup_phy() and phylink_disconnect_phy() are called. But since phylink_disconnect_phy() runs under rtnl_lock(), it would deadlock with phylink_resolve() when calling flush_work(&pl->resolve). Additionally, it would have been undesirable because it would have unnecessarily blocked many other call paths as well in the entire kernel, so the smaller-scoped lock was preferred.

CVSS metrics

5 scores · 5 sources · 1 version

EPSS trend

Probability

0.11%

Chance of exploitation in the next 30 days

Percentile

1%

Versus all other CVEs

30-day change

No change 0.00 pp

From 0.11% on 04-10-2026

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Version check

Known conditions: local access, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.

Ubuntu151 products
  • linuxAll versions (No fix recorded)
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-awsAll versions (No fix recorded)
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Chainguard5 products
  • linux-aws-6.12< 6.12.62-r1 | < 6.12.71-r0 | < 6.12.77-r2 | < 6.12.67-r0 | < 6.12.77-r0 | < 6.12.68-r1 | < 6.12.65-r2 | < 6.12.65-r1 | < 6.12.80-r0 | < 6.12.65-r0 | < 6.12.72-r0 | < 6.12.77-r1 | < 6.12.68-r0 | < 6.12.70-r0 | < 6.12.78-r0 | < 6.12.63-r0 | < 6.12.74-r1 | < 6.12.69-r0 | < 6.12.62-r2 | < 6.12.72-r1 | < 6.12.76-r0 | < 6.12.66-r0 | < 6.12.74-r0
  • linux-azure-6.12< 6.12.68-r0 | < 6.12.65-r1 | < 6.12.69-r0 | < 6.12.65-r4 | < 6.12.65-r3 | < 6.12.74-r1 | < 6.12.62-r1 | < 6.12.67-r0 | < 6.12.76-r0 | < 6.12.70-r0 | < 6.12.74-r0 | < 6.12.66-r0 | < 6.12.62-r2 | < 6.12.77-r0 | < 6.12.72-r0 | < 6.12.77-r1 | < 6.12.77-r2 | < 6.12.65-r2 | < 6.12.78-r0 | < 6.12.63-r0 | < 6.12.71-r0 | < 6.12.80-r0
  • linux-gcp-6.12< 6.12.70-r0 | < 6.12.66-r0 | < 6.12.74-r1 | < 6.12.69-r0 | < 6.12.76-r0 | < 6.12.68-r1 | < 6.12.62-r0 | < 6.12.65-r1 | < 6.12.62-r2 | < 6.12.78-r0 | < 6.12.62-r1 | < 6.12.74-r0 | < 6.12.63-r0 | < 6.12.77-r0 | < 6.12.72-r0 | < 6.12.65-r2 | < 6.12.65-r0 | < 6.12.80-r0 | < 6.12.67-r0 | < 6.12.68-r0 | < 6.12.71-r0 | < 6.12.77-r2 | < 6.12.77-r1
  • linux-qemu-6.12< 6.12.65-r2 | < 6.12.74-r1 | < 6.12.68-r0 | < 6.12.77-r1 | < 6.12.78-r0 | < 6.12.74-r0 | < 6.12.71-r0 | < 6.12.77-r2 | < 6.12.80-r0 | < 6.12.72-r0 | < 6.12.65-r1 | < 6.12.67-r0 | < 6.12.77-r0 | < 6.12.66-r0 | < 6.12.76-r0 | < 6.12.69-r0 | < 6.12.70-r0
  • linux-vmware-6.12< 6.12.78-r0 | < 6.12.74-r1 | < 6.12.66-r0 | < 6.12.65-r1 | < 6.12.65-r2 | < 6.12.77-r1 | < 6.12.69-r0 | < 6.12.70-r0 | < 6.12.77-r2 | < 6.12.80-r0 | < 6.12.68-r1 | < 6.12.72-r0 | < 6.12.71-r0 | < 6.12.67-r0 | < 6.12.74-r0 | < 6.12.68-r0 | < 6.12.77-r0 | < 6.12.76-r0
Linux2 products
  • linux≥ 5fd0f1a02e750e2db4038dee60edea669ce5aab1, < 56fe63b05ec84ae6674269d78397cec43a7a295a | ≥ 5fd0f1a02e750e2db4038dee60edea669ce5aab1, < 0ba5b2f2c381dbec9ed9e4ab3ae5d3e667de0dc3 | 6.14
  • linux_kernel< 6.16.8 | 6.17:rc1 | 6.17:rc2 | 6.17:rc3 | 6.17:rc4 | 6.17:rc5
Debian1 product
  • linux< 6.16.8-1

4 vendors · 159 products

References

9 links