CVE-2025-39905: net: phylink: add lock for serializing concurrent pl->phydev writes with resolver
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.11% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 0ba5b2f2c381dbec9ed9e4ab3ae5d3e667de0dc3, 56fe63b05ec84ae6674269d78397cec43a7a295a; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 0ba5b2f2c381dbec9ed9e4ab3ae5d3e667de0dc3, 56fe63b05ec84ae6674269d78397cec43a7a295a; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 1, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-362
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.0
- CNA · Linux
- 7.0
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.14affected
- 5fd0f1a02e750e2db4038dee60edea669ce5aab1 and later · before 56fe63b05ec84ae6674269d78397cec43a7a295aaffected · git
- 5fd0f1a02e750e2db4038dee60edea669ce5aab1 and later · before 0ba5b2f2c381dbec9ed9e4ab3ae5d3e667de0dc3affected · git
- before 6.14not affected · semver
- 6.16.8 and later · up to and including 6.16.*not affected · semver
- 6.17 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 6.16.8
- linux linux kernel6.17
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-124.27.1.el10_1 | 6.12.0-124.27.1.el10_1 |
| AlmaLinux:10 | kernel-doc | before 6.12.0-124.27.1.el10_1 | 6.12.0-124.27.1.el10_1 |
| Debian:14 | linux | before 6.16.8-1 | 6.16.8-1 |
| Red Hat:enterprise_linux:10.1 | kernel | before 0:6.12.0-124.27.1.el10_1 | 0:6.12.0-124.27.1.el10_1 |
| Red Hat:enterprise_linux:10.1 | kernel-64k | before 0:6.12.0-124.27.1.el10_1 | 0:6.12.0-124.27.1.el10_1 |
| Red Hat:enterprise_linux:10.1 | kernel-64k-core | before 0:6.12.0-124.27.1.el10_1 | 0:6.12.0-124.27.1.el10_1 |
| Red Hat:enterprise_linux:10.1 | kernel-64k-debug | before 0:6.12.0-124.27.1.el10_1 | 0:6.12.0-124.27.1.el10_1 |
| Red Hat:enterprise_linux:10.1 | kernel-64k-debug-core | before 0:6.12.0-124.27.1.el10_1 | 0:6.12.0-124.27.1.el10_1 |
| Red Hat:enterprise_linux:10.1 | kernel-64k-debug-debuginfo | before 0:6.12.0-124.27.1.el10_1 | 0:6.12.0-124.27.1.el10_1 |
| Red Hat:enterprise_linux:10.1 | kernel-64k-debug-devel | before 0:6.12.0-124.27.1.el10_1 | 0:6.12.0-124.27.1.el10_1 |
| Red Hat:enterprise_linux:10.1 | kernel-64k-debug-devel-matched | before 0:6.12.0-124.27.1.el10_1 | 0:6.12.0-124.27.1.el10_1 |
| Red Hat:enterprise_linux:10.1 | kernel-64k-debug-modules | before 0:6.12.0-124.27.1.el10_1 | 0:6.12.0-124.27.1.el10_1 |
| Red Hat:enterprise_linux:10.1 | kernel-64k-debug-modules-core | before 0:6.12.0-124.27.1.el10_1 | 0:6.12.0-124.27.1.el10_1 |
| Red Hat:enterprise_linux:10.1 | kernel-64k-debug-modules-extra | before 0:6.12.0-124.27.1.el10_1 | 0:6.12.0-124.27.1.el10_1 |
| Red Hat:enterprise_linux:10.1 | kernel-64k-debuginfo | before 0:6.12.0-124.27.1.el10_1 | 0:6.12.0-124.27.1.el10_1 |
| Red Hat:enterprise_linux:10.1 | kernel-64k-devel | before 0:6.12.0-124.27.1.el10_1 | 0:6.12.0-124.27.1.el10_1 |
| Red Hat:enterprise_linux:10.1 | kernel-64k-devel-matched | before 0:6.12.0-124.27.1.el10_1 | 0:6.12.0-124.27.1.el10_1 |
| Red Hat:enterprise_linux:10.1 | kernel-64k-modules | before 0:6.12.0-124.27.1.el10_1 | 0:6.12.0-124.27.1.el10_1 |
| Red Hat:enterprise_linux:10.1 | kernel-64k-modules-core | before 0:6.12.0-124.27.1.el10_1 | 0:6.12.0-124.27.1.el10_1 |
| Red Hat:enterprise_linux:10.1 | kernel-64k-modules-extra | before 0:6.12.0-124.27.1.el10_1 | 0:6.12.0-124.27.1.el10_1 |
| Red Hat:enterprise_linux:10.1 | kernel-abi-stablelists | before 0:6.12.0-124.27.1.el10_1 | 0:6.12.0-124.27.1.el10_1 |
| Red Hat:enterprise_linux:10.1 | kernel-core | before 0:6.12.0-124.27.1.el10_1 | 0:6.12.0-124.27.1.el10_1 |
| Red Hat:enterprise_linux:10.1 | kernel-debug | before 0:6.12.0-124.27.1.el10_1 | 0:6.12.0-124.27.1.el10_1 |
| Red Hat:enterprise_linux:10.1 | kernel-debug-core | before 0:6.12.0-124.27.1.el10_1 | 0:6.12.0-124.27.1.el10_1 |
+70
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-50420Oct 1, 2025 · crypto: hisilicon/hpre - fix resource leak in remove process22Monitor
- ← EarlierCVE-2025-39904Oct 1, 2025 · arm64: kexec: initialize kexec_buf struct in load_other_segments()22Monitor
- Later →CVE-2022-50421Oct 1, 2025 · rpmsg: char: Avoid double destroy of default endpoint31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0ba5b2f2c381dbec9ed9e4ab3ae5d3e667de0dc3 | Vendor (CNA) |
| Linux Linux | 56fe63b05ec84ae6674269d78397cec43a7a295a | Vendor (CNA) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| almalinux:kernel-abi-stablelists | 6.12.0-124.27.1.el10_1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-doc | 6.12.0-124.27.1.el10_1 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.16.8-1 · Debian:14 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:6.12.0-124.27.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:6.12.0-124.27.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:6.12.0-124.27.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:6.12.0-124.27.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:6.12.0-124.27.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:6.12.0-124.27.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:6.12.0-124.27.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:6.12.0-124.27.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:6.12.0-124.27.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:6.12.0-124.27.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:6.12.0-124.27.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| red hat:kernel-debuginfo-common-ppc64le | 0:6.12.0-124.27.1.el10_1 · Red Hat:enterprise_linux:10.1 | Package registry (OSV) |
| rocky linux:kernel | 0:6.12.0-124.27.1.el10_1 · Rocky Linux:10 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.