# CVE-2026-72037: net: lan743x: Initialize eth_syslock spinlock before use

> A missing spinlock initialization in the lan743x driver can cause a kernel crash during device probe when debug options are enabled.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-72037, DEBIAN-CVE-2026-72037, GHSA-57rg-9qx8-7v7g, UBUNTU-CVE-2026-72037

## What is CVE-2026-72037?

CVE-2026-72037 is a vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-72037?


## How do I fix CVE-2026-72037?

Apply the vendor's patch.

## Is CVE-2026-72037 being exploited?

There is no known exploitation of CVE-2026-72037 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72037 and fix it if it is affected.

What it is: CVE-2026-72037 is a vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72037 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72037/ (Markdown: https://insights.sbomify.com/CVE-2026-72037/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72037
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72037
- OSV: https://osv.dev/vulnerability/CVE-2026-72037

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72037/
Summaries are generated and may contain mistakes; the official description above is the record.