In the Linux kernel, the following vulnerability has been resolved: net: lan743x: Initialize eth_syslock spinlock before use lan743x_hardware_init()… (CVE-2026-72037)
A vulnerability in the Linux kernel's lan743x network driver was resolved by ensuring the eth_syslock spinlock is initialized before use. The issue occurred because the spinlock was only initialized after reading the strap status during hardware initialization, causing potential spinlock debug check failures with CONFIG_DEBUG_SPINLOCK enabled. The fix initializes the spinlock earlier to prevent locking an uninitialized spinlock.
AI Analysis
Technical Summary
The Linux kernel's lan743x driver had a flaw where the eth_syslock spinlock was not initialized before being acquired during the PCI11x1x probe sequence. Specifically, lan743x_hardware_init() calls pci11x1x_strap_get_status(), which acquires the Ethernet subsystem hardware lock via lan743x_hs_syslock_acquire(), relying on adapter->eth_syslock_spinlock. Since the spinlock was initialized only after reading the strap status, attempts to lock it beforehand could trigger spinlock debug checks when CONFIG_DEBUG_SPINLOCK is enabled. The vulnerability was fixed by initializing the spinlock before reading the strap status, ensuring the probe path never locks an uninitialized spinlock.
Potential Impact
This vulnerability could cause kernel spinlock debug check failures, potentially leading to kernel warnings or crashes during hardware initialization in affected configurations. It does not indicate direct code execution or privilege escalation but may affect system stability during network driver initialization.
Mitigation Recommendations
A fix has been implemented to initialize the eth_syslock spinlock before its first use in the lan743x driver. Users should apply the updated Linux kernel version containing this fix. Since this is a kernel-level fix, upgrading to the patched kernel version is the recommended remediation. Patch status is not explicitly confirmed in the provided data; users should consult the official Linux kernel advisories or vendor patches for the exact fixed versions and apply updates accordingly.
In the Linux kernel, the following vulnerability has been resolved: net: lan743x: Initialize eth_syslock spinlock before use lan743x_hardware_init()… (CVE-2026-72037)
Description
A vulnerability in the Linux kernel's lan743x network driver was resolved by ensuring the eth_syslock spinlock is initialized before use. The issue occurred because the spinlock was only initialized after reading the strap status during hardware initialization, causing potential spinlock debug check failures with CONFIG_DEBUG_SPINLOCK enabled. The fix initializes the spinlock earlier to prevent locking an uninitialized spinlock.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's lan743x driver had a flaw where the eth_syslock spinlock was not initialized before being acquired during the PCI11x1x probe sequence. Specifically, lan743x_hardware_init() calls pci11x1x_strap_get_status(), which acquires the Ethernet subsystem hardware lock via lan743x_hs_syslock_acquire(), relying on adapter->eth_syslock_spinlock. Since the spinlock was initialized only after reading the strap status, attempts to lock it beforehand could trigger spinlock debug checks when CONFIG_DEBUG_SPINLOCK is enabled. The vulnerability was fixed by initializing the spinlock before reading the strap status, ensuring the probe path never locks an uninitialized spinlock.
Potential Impact
This vulnerability could cause kernel spinlock debug check failures, potentially leading to kernel warnings or crashes during hardware initialization in affected configurations. It does not indicate direct code execution or privilege escalation but may affect system stability during network driver initialization.
Mitigation Recommendations
A fix has been implemented to initialize the eth_syslock spinlock before its first use in the lan743x driver. Users should apply the updated Linux kernel version containing this fix. Since this is a kernel-level fix, upgrading to the patched kernel version is the recommended remediation. Patch status is not explicitly confirmed in the provided data; users should consult the official Linux kernel advisories or vendor patches for the exact fixed versions and apply updates accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-57rg-9qx8-7v7g
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-72037"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a808b78bf8831d539501dd9
Added to database: 08/15/2026, 15:53:28 UTC
Last enriched: 08/15/2026, 17:07:38 UTC
Last updated: 08/16/2026, 00:41:15 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.