Heimdall Security Logo

CVE-2026-43340

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <2.6.29, <=6.12.*, <430291d8f3884f57ae0057049b0ca291453e29e1, <83134a7a176ce5b4b19b6edecf4360e8d98d1a5a, <4b9a9a6d71e3e252032f959fb3895a33acb5865c, <c01bcc67a9a692d65508ebd480405b5e77d562b7, 0, ed9eccbe8970f6eedc1b978c157caf1251a896d4, 6.6.134, 7.0, <3181c34b415c5464be9d34bff3e43ef63b747039, <2b1f49e4fdff3ef0f8e9158bbb5b149e06287560, <4d5ffe524903a30e2e0da7d16841a56bec2de55c, 2.6.29, <=5.10.*, <=6.6.*, <=6.19.*, 5.15.203, <=6.18.*, 6.12.81, <=*, 5.10.253, <=5.15.*, 6.1.168, 6.18.22, <b89c026227712c367950bbae055a5b31073d3b30, 6.19.12

Description

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.

Gravité et risque d'exploitation

CVE-2026-43340 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.16 %, ce qui la place devant 5.1 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <2.6.29, <=6.12.*, <430291d8f3884f57ae0057049b0ca291453e29e1, <83134a7a176ce5b4b19b6edecf4360e8d98d1a5a, <4b9a9a6d71e3e252032f959fb3895a33acb5865c, <c01bcc67a9a692d65508ebd480405b5e77d562b7, 0, ed9eccbe8970f6eedc1b978c157caf1251a896d4, 6.6.134, 7.0, <3181c34b415c5464be9d34bff3e43ef63b747039, <2b1f49e4fdff3ef0f8e9158bbb5b149e06287560, <4d5ffe524903a30e2e0da7d16841a56bec2de55c, 2.6.29, <=5.10.*, <=6.6.*, <=6.19.*, 5.15.203, <=6.18.*, 6.12.81, <=*, 5.10.253, <=5.15.*, 6.1.168, 6.18.22, <b89c026227712c367950bbae055a5b31073d3b30, 6.19.12) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE