{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72037 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-72037 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-72037 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-72037/ (Markdown: https://insights.sbomify.com/CVE-2026-72037/index.md)","id":"CVE-2026-72037","markdown":"https://insights.sbomify.com/CVE-2026-72037/index.md","name":"CVE-2026-72037","record":{"aliases":["BELL-CVE-2026-72037","DEBIAN-CVE-2026-72037","GHSA-57rg-9qx8-7v7g","UBUNTU-CVE-2026-72037"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A missing spinlock initialization in the lan743x driver can cause a kernel crash during device probe when debug options are enabled.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet: lan743x: Initialize eth_syslock spinlock before use\n\nlan743x_hardware_init() calls pci11x1x_strap_get_status() during the\nPCI11x1x probe sequence. That helper acquires the Ethernet subsystem\nhardware lock via lan743x_hs_syslock_acquire(), which relies on\nadapter-\u003eeth_syslock_spinlock to serialize access.\n\nThe spinlock is currently initialized only after the strap status is\nread. With CONFIG_DEBUG_SPINLOCK enabled, taking the zeroed initialized\nspinlock can trip the spinlock debug check.\n\nFix by initializing adapter-\u003eeth_syslock_spinlock before reading the\nstrap status so the probe path never attempts to lock an uninitialized\nspinlock.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"net: lan743x: Initialize eth_syslock spinlock before use","id":"CVE-2026-72037","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"net: liquidio: fix BAR resource leak on PF number failure","id":"CVE-2026-72038"},"packages":[],"prev":{"headline":"net/sched: sch_multiq: Replace direct dequeue call with peek and qdisc_dequeue_peeked","id":"CVE-2026-72036"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A missing spinlock initialization in the lan743x driver can cause a kernel crash during device probe when debug options are enabled.","url":"https://insights.sbomify.com/CVE-2026-72037/"}