CVE-2026-72037

net: lan743x: Initialize eth_syslock spinlock before use

N/A
Published: August 15, 2026 at 05:51 AM UTC
Updated: August 17, 2026 at 06:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: net: lan743x: Initialize eth_syslock spinlock before use lan743x_hardware_init() calls pci11x1x_strap_get_status() during the PCI11x1x probe sequence. That helper acquires the Ethernet subsystem hardware lock via lan743x_hs_syslock_acquire(), which relies on adapter->eth_syslock_spinlock to serialize access. The spinlock is currently initialized only after the strap status is read. With CONFIG_DEBUG_SPINLOCK enabled, taking the zeroed initialized spinlock can trip the spinlock debug check. Fix by initializing adapter->eth_syslock_spinlock before reading the strap status so the probe path never attempts to lock an uninitialized spinlock.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.0 ≤ v < 6.1.1786.0 ≤ v < 6.12.976.0 ≤ v < 6.18.406.0 ≤ v < 6.6.1456.0 ≤ v < 7.1.56.0 ≤ v < 7.246b777ad9a8c269113634cee6a380bc4e53f39646.0
Vendor states this is fixed in 39139b1c1c2b614096519b526112c726adb12ff0 (fixed)
Vendor states this is fixed in 6523daa6852b1bfef32ec7a105b0217e8a115687 (fixed)
Vendor states this is fixed in 99a6f37b113c46815deb160c5012073563679ef4 (fixed)
Vendor states this is fixed in b6a93a42e0e61f0ba0005a942ee3bffb16c0574e (fixed)
Vendor states this is fixed in b99e890e6b32ffa11c145a16fefcf2c7137a9578 (fixed)
Vendor states this is fixed in dfaefd9a7808736fcd2ed0de108f55c4badc15cc (fixed)
Vendor states this is fixed in 6.0 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card