CVE-2025-40347: net: enetc: fix the deadlock of enetc_mdio_lock
Noroxi assessment
Priority: Monitor (action score 30/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.52% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1f92f5bd057a4fad9dab6af17963cdd21e5da6ed, 2781ca82ce8cad263d80b617addb727e6a84c9e5, 2e55a49dc3b2a6b23329e4fbbd8a5feb20e220aa.
Low priority for now. Upgrade to Linux Linux 1f92f5bd057a4fad9dab6af17963cdd21e5da6ed, 2781ca82ce8cad263d80b617addb727e6a84c9e5, 2e55a49dc3b2a6b23329e4fbbd8a5feb20e220aa 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: enetc: fix the deadlock of enetc_mdio_lock After applying the workaround for err050089, the LS1028A platform experiences RCU stalls on RT kernel. This issue is caused by the recursive acquisition of the read lock enetc_mdio_lock. Here list some of the call stacks identified under the enetc_poll path that may lead to a deadlock: enetc_poll -> enetc_lock_mdio -> enetc_clean_rx_ring OR napi_complete_done -> napi_gro_receive -> enetc_start_xmit -> enetc_lock_mdio -> enetc_map_tx_buffs -> enetc_unlock_mdio -> enetc_unlock_mdio After enetc_poll acquires the read lock, a higher-priority writer attempts to acquire the lock, causing preemption. The writer detects that a read lock is already held and is scheduled out. However, readers under enetc_poll cannot acquire the read lock again because a writer is already waiting, leading to a thread hang. Currently, the deadlock is avoided by adjusting enetc_lock_mdio to prevent recursive lock acquisition.
- Published
- Dec 16, 2025
- Updated
- Oct 14, 2026
- EPSS
- 0.5% · 44th percentile
- CWE
- —
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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.
—
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
- bf9c564716a13dde6a990d3b02c27cd6e39608bf, ff966263f5f9fdf9740f03fed0762ce73c230a6a, 5.12affected
- 6d36ecdbc4410e61a0e02adc5d3abeee22a8ffd3 and later · before a649161526736f48bcc592e3a412e5bcd7dd9e24affected · git
- 6d36ecdbc4410e61a0e02adc5d3abeee22a8ffd3 and later · before 2781ca82ce8cad263d80b617addb727e6a84c9e5affected · git
- 6d36ecdbc4410e61a0e02adc5d3abeee22a8ffd3 and later · before 1f92f5bd057a4fad9dab6af17963cdd21e5da6edaffected · git
- 6d36ecdbc4410e61a0e02adc5d3abeee22a8ffd3 and later · before 2e55a49dc3b2a6b23329e4fbbd8a5feb20e220aaaffected · git
- 6d36ecdbc4410e61a0e02adc5d3abeee22a8ffd3 and later · before 50bd33f6b3922a6b760aa30d409cae891cec8fb5affected · git
- 5.10.24 and later · before 5.11affected · semver
- 5.11.7 and later · before 5.12affected · semver
- before 5.12not affected · semver
- 6.1.175 and later · up to and including 6.1.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.176-1 | 6.1.176-1 |
| Debian:13 | linux | before 6.12.57-1 | 6.12.57-1 |
| Debian:14 | linux | before 6.17.6-1 | 6.17.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-68310Dec 16, 2025 · s390/pci: Avoid deadlock between PCI error recovery and mlx5 crdump0Monitor
- ← EarlierCVE-2025-40346Dec 16, 2025 · arch_topology: Fix incorrect error check in topology_parse_cpu_capacity()0Monitor
- Later →CVE-2025-40348Dec 16, 2025 · slab: Avoid race on slab->obj_exts in alloc_slab_obj_exts0Monitor
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 | 1f92f5bd057a4fad9dab6af17963cdd21e5da6ed | Vendor (CNA) |
| Linux Linux | 2781ca82ce8cad263d80b617addb727e6a84c9e5 | Vendor (CNA) |
| Linux Linux | 2e55a49dc3b2a6b23329e4fbbd8a5feb20e220aa | Vendor (CNA) |
| Linux Linux | 5.11 | Vendor (CNA) |
| Linux Linux | 5.12 | Vendor (CNA) |
| Linux Linux | 50bd33f6b3922a6b760aa30d409cae891cec8fb5 | Vendor (CNA) |
| Linux Linux | a649161526736f48bcc592e3a412e5bcd7dd9e24 | Vendor (CNA) |
| debian:linux | 6.1.176-1 · Debian:12 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.