Skip to main content
CVE-2026-43319VulnerabilityPublished Updated

Microsoft · spi: spidev: fix lock inversion between spi_lock and buf_lock

Affects MicrosoftSource GCVE Database

0
Compare

Not known to be exploited.

Data as of 30 Oct 2026, 06:59 UTC

Severity
Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.09% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Microsoft Security Response Center MicrosoftAffected
  • =3.0
  • Microsoft
  • Azure Linux
  • 3.0
  • Azure Linux 3.0
  • kernel
Fixed in–

Description

CVE-2026-43319 addresses a lock inversion issue between spi_lock and buf_lock in Microsoft software version 3.0. The vulnerability involves improper locking order that could potentially lead to deadlocks or other concurrency issues. No CVSS score or detailed impact information is provided. There is no indication of known exploits in the wild or available patches at this time.

References

Community reviews

Loading reviews…