Answer in brief
CVE-2026-72037 records a Unknown severity vulnerability in net: lan743x: Initialize eth_syslock spinlock before use. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=46b777ad9a8c269113634cee6a380bc4e53f3964 <dfaefd9a7808736fcd2ed0de108f55c4badc15cc || >=46b777ad9a8c269113634cee6a380bc4e53f3964 <6523daa6852b1bfef32ec7a105b0217e8a115687 || >=46b777ad9a8c269113634cee6a380bc4e53f3964 <b6a93a42e0e61f0ba0005a942ee3bffb16c0574e || >=46b777ad9a8c269113634cee6a380bc4e53f3964 <99a6f37b113c46815deb160c5012073563679ef4 || >=46b777ad9a8c269113634cee6a380bc4e53f3964 <b99e890e6b32ffa11c145a16fefcf2c7137a9578 || >=46b777ad9a8c269113634cee6a380bc4e53f3964 <39139b1c1c2b614096519b526112c726adb12ff0 | dfaefd9a7808736fcd2ed0de108f55c4badc15cc, 6523daa6852b1bfef32ec7a105b0217e8a115687, b6a93a42e0e61f0ba0005a942ee3bffb16c0574e, 99a6f37b113c46815deb160c5012073563679ef4, b99e890e6b32ffa11c145a16fefcf2c7137a9578, 39139b1c1c2b614096519b526112c726adb12ff0 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-72037 records a Unknown severity vulnerability in net: lan743x: Initialize eth_syslock spinlock before use. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=46b777ad9a8c269113634cee6a380bc4e53f3964 <dfaefd9a7808736fcd2ed0de108f55c4badc15cc || >=46b777ad9a8c269113634cee6a380bc4e53f3964 <6523daa6852b1bfef32ec7a105b0217e8a115687 || >=46b777ad9a8c269113634cee6a380bc4e53f3964 <b6a93a42e0e61f0ba0005a942ee3bffb16c0574e || >=46b777ad9a8c269113634cee6a380bc4e53f3964 <99a6f37b113c46815deb160c5012073563679ef4 || >=46b777ad9a8c269113634cee6a380bc4e53f3964 <b99e890e6b32ffa11c145a16fefcf2c7137a9578 || >=46b777ad9a8c269113634cee6a380bc4e53f3964 <39139b1c1c2b614096519b526112c726adb12ff0 | dfaefd9a7808736fcd2ed0de108f55c4badc15cc, 6523daa6852b1bfef32ec7a105b0217e8a115687, b6a93a42e0e61f0ba0005a942ee3bffb16c0574e, 99a6f37b113c46815deb160c5012073563679ef4, b99e890e6b32ffa11c145a16fefcf2c7137a9578, 39139b1c1c2b614096519b526112c726adb12ff0 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.