Skip to content
Noroxi
CVE-2026-43340· NVD / CVE Program· CNA Linux

comedi: Reinit dev->spinlock between attachments to low-level drivers

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 2b1f49e4fdff3ef0f8e9158bbb5b149e06287560, 3181c34b415c5464be9d34bff3e43ef63b747039, 430291d8f3884f57ae0057049b0ca291453e29e1.

Low priority for now. Upgrade to Linux Linux 2b1f49e4fdff3ef0f8e9158bbb5b149e06287560, 3181c34b415c5464be9d34bff3e43ef63b747039, 430291d8f3884f57ae0057049b0ca291453e29e1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: comedi: Reinit dev->spinlock between attachments to low-level drivers `struct comedi_device` is the main controlling structure for a COMEDI device created by the COMEDI subsystem. It contains a member `spinlock` containing a spin-lock that is initialized by the COMEDI subsystem, but is reserved for use by a low-level driver attached to the COMEDI device (at least since commit 25436dc9d84f ("Staging: comedi: remove RT code")). Some COMEDI devices (those created on initialization of the COMEDI subsystem when the "comedi.comedi_num_legacy_minors" parameter is non-zero) can be attached to different low-level drivers over their lifetime using the `COMEDI_DEVCONFIG` ioctl command. This can result in inconsistent lock states being reported when there is a mismatch in the spin-lock locking levels used by each low-level driver to which the COMEDI device has been attached. Fix it by reinitializing `dev->spinlock` before calling the low-level driver's `attach` function pointer if `CONFIG_LOCKDEP` is enabled.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 8, 2026
Updated
Jun 17, 2026
EPSS
0.1% · 5th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-43340

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel2.6.29 and later · before 5.10.253
  • linux linux kernel5.11 and later · before 5.15.203
  • linux linux kernel5.16 and later · before 6.1.168
  • linux linux kernel6.2 and later · before 6.6.134
  • linux linux kernel6.7 and later · before 6.12.81
  • linux linux kernel6.13 and later · before 6.18.22
  • linux linux kernel6.19 and later · before 6.19.12
  • linux linux kernel7.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.29affected
    • ed9eccbe8970f6eedc1b978c157caf1251a896d4 and later · before 3181c34b415c5464be9d34bff3e43ef63b747039affected · git
    • ed9eccbe8970f6eedc1b978c157caf1251a896d4 and later · before 2b1f49e4fdff3ef0f8e9158bbb5b149e06287560affected · git
    • ed9eccbe8970f6eedc1b978c157caf1251a896d4 and later · before 4d5ffe524903a30e2e0da7d16841a56bec2de55caffected · git
    • ed9eccbe8970f6eedc1b978c157caf1251a896d4 and later · before c01bcc67a9a692d65508ebd480405b5e77d562b7affected · git
    • ed9eccbe8970f6eedc1b978c157caf1251a896d4 and later · before 430291d8f3884f57ae0057049b0ca291453e29e1affected · git
    • ed9eccbe8970f6eedc1b978c157caf1251a896d4 and later · before b89c026227712c367950bbae055a5b31073d3b30affected · git
    • ed9eccbe8970f6eedc1b978c157caf1251a896d4 and later · before 83134a7a176ce5b4b19b6edecf4360e8d98d1a5aaffected · git
    • ed9eccbe8970f6eedc1b978c157caf1251a896d4 and later · before 4b9a9a6d71e3e252032f959fb3895a33acb5865caffected · git
    • before 2.6.29not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.170-16.1.170-1
Debian:13linuxbefore 6.12.85-16.12.85-1
Debian:14linuxbefore 6.19.12-16.19.12-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-43335May 8, 2026 · interconnect: qcom: sm8450: Fix NULL pointer dereference in icc_link_nodes()
    22Monitor
  • ← EarlierCVE-2026-43336May 8, 2026 · lib/crypto: chacha: Zeroize permuted_state before it leaves scope
    30Monitor
  • Later →CVE-2026-43342May 8, 2026 · usb: gadget: f_rndis: Protect RNDIS options with mutex
    18Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux2b1f49e4fdff3ef0f8e9158bbb5b149e06287560Vendor (CNA)
Linux Linux3181c34b415c5464be9d34bff3e43ef63b747039Vendor (CNA)
Linux Linux430291d8f3884f57ae0057049b0ca291453e29e1Vendor (CNA)
Linux Linux4b9a9a6d71e3e252032f959fb3895a33acb5865cVendor (CNA)
Linux Linux4d5ffe524903a30e2e0da7d16841a56bec2de55cVendor (CNA)
Linux Linux83134a7a176ce5b4b19b6edecf4360e8d98d1a5aVendor (CNA)
Linux Linuxb89c026227712c367950bbae055a5b31073d3b30Vendor (CNA)
Linux Linuxc01bcc67a9a692d65508ebd480405b5e77d562b7Vendor (CNA)
debian:linux6.1.170-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records