CVE-2025-40347 Details
Description
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.
A deadlock vulnerability has been identified in the Linux kernel ENETC (Ethernet Network Controller) driver, specifically on the LS1028A platform running a real-time (RT) kernel. The issue arises from the recursive acquisition of a read lock, enetc_mdio_lock, which leads to a thread hang. This deadlock occurs when the enetc_poll function acquires the read lock, and a higher-priority writer attempts to acquire the lock, causing preemption. The writer, finding the read lock already held, is scheduled out. Meanwhile, readers in the enetc_poll context cannot reacquire the read lock because a writer is waiting, resulting in a deadlock. Call stacks under the enetc_poll path have been identified that may lead to this deadlock.
The deadlock has been addressed by modifying the ENETC driver to prevent recursive acquisitions of the MDIO lock. Users should ensure they are running a version of the Linux kernel that includes this fix.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Dec 16, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/1f92f5bd057a4fad9dab6af17963cdd21e5da6ed | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/2781ca82ce8cad263d80b617addb727e6a84c9e5 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/2e55a49dc3b2a6b23329e4fbbd8a5feb20e220aa | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/50bd33f6b3922a6b760aa30d409cae891cec8fb5 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/a649161526736f48bcc592e3a412e5bcd7dd9e24 | kernel.org |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 14, 2026 | CVE Translated | [email protected] |
| Jul 30, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 1, 2026 | CVE Modified | kernel.org |
| Dec 16, 2025 | New CVE Received | kernel.org |
Volerion