CVE-2026-43319

Local operation hang via spidev lock inversion

Published May 8, 2026 · Updated May 8, 2026

Improper locking in the Linux Kernel spidev driver allows local users to deadlock concurrent device operations through one file descriptor. The read and write paths take buf_lock before spi_lock, while spidev_ioctl takes the same locks in reverse order, creating an AB-BA cycle. Triggering the flaw requires concurrent read or write and SPI_IOC_WR_MAX_SPEED_HZ ioctl calls on the same open spidev device; affected operations hang without reported data disclosure or modification.

CVSS severity5.5
Medium
EPSS probability0.09%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper locking in the Linux Kernel spidev driver allows local users to deadlock concurrent device operations through one file descriptor. The read and write paths take buf_lock before spi_lock, while spidev_ioctl takes the same locks in reverse order, creating an AB-BA cycle. Triggering the flaw requires concurrent read or write and SPI_IOC_WR_MAX_SPEED_HZ ioctl calls on the same open spidev device; affected operations hang without reported data disclosure or modification.

The record

CVE
CVE-2026-43319
Published
May 8, 2026
Updated
May 8, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
CWE-667, T1499
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. May 8, 2026CVE publishedPublication date reported by the CVE source.
  2. May 8, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <40534d19ed2afb880ecf202dab26a8e7a5808d16
  2. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <41ccfac7d302968a4f32b5f7b012d066c5f5cdf8
  3. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e341e18215030af2136836b78508e0d798916df7
  4. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f8431b8672231d378b03176fe74c95adfd3522cf

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <40534d19ed2afb880ecf202dab26a8e7a5808d16; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <41ccfac7d302968a4f32b5f7b012d066c5f5cdf8; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e341e18215030af2136836b78508e0d798916df7; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f8431b8672231d378b03176fe74c95adfd3522cf

Published CVSS scores

5.5NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-667Improper Locking
T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo