VulnerabilityPublished 8 May 2026Updated 6 Nov 2026

CVE-2026-43319: Linux kernel · spi: spidev: fix lock inversion between spi_lock and buf_lock

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in fabfed1afe273717ea33b8aee46b767360edbb80 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:04 UTC

Severity

Unrated

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

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch

Available – fixed in fabfed1afe273717ea33b8aee46b767360edbb80, f8431b8672231d378b03176fe74c95adfd3522cf, e341e18215030af2136836b78508e0d798916df7 +2

Exploitation evidence

Disclosed: evidence found.
CVE published 8 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ a720416d94634068951773cb9e9d6f1b73769e5b, < fabfed1afe273717ea33b8aee46b767360edbb80	Fixed in fabfed1afe273717ea33b8aee46b767360edbb80
LinuxLinux	Affected ≥ a720416d94634068951773cb9e9d6f1b73769e5b, < f8431b8672231d378b03176fe74c95adfd3522cf	Fixed in f8431b8672231d378b03176fe74c95adfd3522cf
LinuxLinux	Affected ≥ a720416d94634068951773cb9e9d6f1b73769e5b, < e341e18215030af2136836b78508e0d798916df7	Fixed in e341e18215030af2136836b78508e0d798916df7
LinuxLinux	Affected ≥ a720416d94634068951773cb9e9d6f1b73769e5b, < 40534d19ed2afb880ecf202dab26a8e7a5808d16	Fixed in 40534d19ed2afb880ecf202dab26a8e7a5808d16
LinuxLinux	Affected ≥ a720416d94634068951773cb9e9d6f1b73769e5b, < 41ccfac7d302968a4f32b5f7b012d066c5f5cdf8	Fixed in 41ccfac7d302968a4f32b5f7b012d066c5f5cdf8
LinuxLinux	Affected =6.2	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: spi: spidev: fix lock inversion between spi_lock and buf_lock The spidev driver previously used two mutexes, spi_lock and buf_lock, but acquired them in different orders depending on the code path: write()/read(): buf_lock -> spi_lock ioctl(): spi_lock -> buf_lock This AB-BA locking pattern triggers lockdep warnings and can cause real deadlocks: WARNING: possible circular locking dependency detected spidev_ioctl() -> mutex_lock(&spidev->buf_lock) spidev_sync_write() -> mutex_lock(&spidev->spi_lock) *** DEADLOCK *** The issue is reproducible with a simple userspace program that performs write() and SPI_IOC_WR_MAX_SPEED_HZ ioctl() calls from separate threads on the same spidev file descriptor. Fix this by simplifying the locking model and removing the lock inversion entirely. spidev_sync() no longer performs any locking, and all callers serialize access using spi_lock. buf_lock is removed since its functionality is fully covered by spi_lock, eliminating the possibility of lock ordering issues. This removes the lock inversion and prevents deadlocks without changing userspace ABI or behaviour.

References

Community reviews

Loading reviews…