CVE-2026-43340

Service interruption via stale COMEDI spinlock state

Published May 8, 2026 · Updated May 8, 2026

Improper lock-state handling in the Linux Kernel COMEDI subsystem allows local users to interrupt service through low-level driver reattachment. comedi_device_attach reuses dev->spinlock across successive COMEDI_DEVCONFIG attachments instead of reinitializing it before a new driver's attach callback, so drivers with different locking levels produce inconsistent lock states. The path requires legacy COMEDI minors, permission to issue COMEDI_DEVCONFIG, attachment to multiple low-level drivers, and CONFIG_LOCKDEP; the reported impact is limited to availability.

CVSS severity5.5
Medium
EPSS probability0.11%
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 lock-state handling in the Linux Kernel COMEDI subsystem allows local users to interrupt service through low-level driver reattachment. comedi_device_attach reuses dev->spinlock across successive COMEDI_DEVCONFIG attachments instead of reinitializing it before a new driver's attach callback, so drivers with different locking levels produce inconsistent lock states. The path requires legacy COMEDI minors, permission to issue COMEDI_DEVCONFIG, attachment to multiple low-level drivers, and CONFIG_LOCKDEP; the reported impact is limited to availability.

The record

CVE
CVE-2026-43340
Published
May 8, 2026
Updated
May 8, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
T1499.004
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=2.6.29
  2. Affected versionversion=ed9eccbe8970f6eedc1b978c157caf1251a896d4 <2b1f49e4fdff3ef0f8e9158bbb5b149e06287560
  3. Affected versionversion=ed9eccbe8970f6eedc1b978c157caf1251a896d4 <3181c34b415c5464be9d34bff3e43ef63b747039
  4. Affected versionversion=ed9eccbe8970f6eedc1b978c157caf1251a896d4 <430291d8f3884f57ae0057049b0ca291453e29e1
  5. Affected versionversion=ed9eccbe8970f6eedc1b978c157caf1251a896d4 <4b9a9a6d71e3e252032f959fb3895a33acb5865c
  6. Affected versionversion=ed9eccbe8970f6eedc1b978c157caf1251a896d4 <4d5ffe524903a30e2e0da7d16841a56bec2de55c
  7. Affected versionversion=ed9eccbe8970f6eedc1b978c157caf1251a896d4 <83134a7a176ce5b4b19b6edecf4360e8d98d1a5a
  8. Affected versionversion=ed9eccbe8970f6eedc1b978c157caf1251a896d4 <b89c026227712c367950bbae055a5b31073d3b30
  9. Affected versionversion=ed9eccbe8970f6eedc1b978c157caf1251a896d4 <c01bcc67a9a692d65508ebd480405b5e77d562b7

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=2.6.29; version=ed9eccbe8970f6eedc1b978c157caf1251a896d4 <2b1f49e4fdff3ef0f8e9158bbb5b149e06287560; version=ed9eccbe8970f6eedc1b978c157caf1251a896d4 <3181c34b415c5464be9d34bff3e43ef63b747039; version=ed9eccbe8970f6eedc1b978c157caf1251a896d4 <430291d8f3884f57ae0057049b0ca291453e29e1; version=ed9eccbe8970f6eedc1b978c157caf1251a896d4 <4b9a9a6d71e3e252032f959fb3895a33acb5865c; version=ed9eccbe8970f6eedc1b978c157caf1251a896d4 <4d5ffe524903a30e2e0da7d16841a56bec2de55c; version=ed9eccbe8970f6eedc1b978c157caf1251a896d4 <83134a7a176ce5b4b19b6edecf4360e8d98d1a5a; version=ed9eccbe8970f6eedc1b978c157caf1251a896d4 <b89c026227712c367950bbae055a5b31073d3b30; version=ed9eccbe8970f6eedc1b978c157caf1251a896d4 <c01bcc67a9a692d65508ebd480405b5e77d562b7

Published CVSS scores

2.3Amazon LinuxCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L
5.5UbuntuCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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

T1499.004Endpoint Denial of Service: Application or System Exploitation

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