Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 2 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 46b777ad9a8c269113634cee6a380bc4e53f3964 – < dfaefd9a7808736fcd2ed0de108f55c4badc15cc
    • affected 46b777ad9a8c269113634cee6a380bc4e53f3964 – < 6523daa6852b1bfef32ec7a105b0217e8a115687
    • affected 46b777ad9a8c269113634cee6a380bc4e53f3964 – < b6a93a42e0e61f0ba0005a942ee3bffb16c0574e
    • affected 46b777ad9a8c269113634cee6a380bc4e53f3964 – < 99a6f37b113c46815deb160c5012073563679ef4
    • affected 46b777ad9a8c269113634cee6a380bc4e53f3964 – < b99e890e6b32ffa11c145a16fefcf2c7137a9578
    • affected 46b777ad9a8c269113634cee6a380bc4e53f3964 – < 39139b1c1c2b614096519b526112c726adb12ff0
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-72037 badge
[![CVE-2026-72037](https://cveledger.app/badge/CVE-2026-72037.svg)](https://cveledger.app/cve/CVE-2026-72037)

Record last updated .