net: lan743x: Initialize eth_syslock spinlock before use
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 46b777ad9a8c269113634cee6a380bc4e53f3964 · < 39139b1c1c2b614096519b526112c726adb12ff0| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The lan743x driver reads PCI11x1x strap status before initializing a spinlock used by that path. With CONFIG_DEBUG_SPINLOCK enabled, this can trip a spinlock debug check during probe. The input does not describe an attacker, an access requirement, or user interaction.
Engineers running the Linux kernel with the lan743x driver should check their deployments; affected versions are not specified.