CVE-2026-80559

Vulnérabilité élevée dans Linux (Linux)

CVSS 7.8 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, <3e8ed76a4f3572e637653f0654cccdf617903231, <5c1c5227c93f18cd329dd754b4df5e0e2daece1e, 5.15.217, 0, <4.1, <83aa12f9f2468a4fbef027c09224dc1011850fb0, <dab741c9da72102a37cc1020a929051b7c45f9fb, <=7.1.*, <=5.10.*, <=6.6.*, 5.10.266, <=6.18.*, 6.1.184, 7.1.10, e831cd251fb91d6c25352d322743db0d17ea11dd, 4.1, <=*, <9da976eb649c9e2f588a4499410e4d8af687925f, <764b507be7b51787e1f577ca3bf0bab7efe81ff8, <=5.15.*, 6.6.153, 6.12.105, 6.18.46, <cd4ecce2fd87760c0ad9a9d28c9fc62ea1dbfd3d, 7.2, <beb9b0bd6e6e23f5e9e42b7ef890a50f57f1f3aa

Description

In the Linux kernel, the following vulnerability has been resolved: Input: sur40 - fix input device registration ordering In sur40_probe(), input_register_device() was previously called early before the V4L2 video device and vb2_queue components were fully initialized. If userspace opened the input device immediately upon registration, sur40_open() would trigger and start the sur40_poll() worker thread. This worker thread invokes sur40_process_video() and accesses the uninitialized vb2_queue structure, leading to a data race and potential system crash. Furthermore, if V4L2 or video registration failed after input_register_device() succeeded, the error path fell through to calling input_free_device() on a successfully registered device instead of input_unregister_device(), corrupting input core state. Move input_register_device() to the very end of sur40_probe(). This ensures the V4L2 and video queue structures are fully initialized before polling can start, and naturally resolves the error path bug since input_free_device() is now only called when input registration has not yet occurred. To maintain strict LIFO (Last-In, First-Out) teardown ordering, also move input_unregister_device() to the very beginning of sur40_disconnect(). This guarantees that the input polling worker thread is stopped before V4L2 video components or control handlers are unregistered.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, <3e8ed76a4f3572e637653f0654cccdf617903231, <5c1c5227c93f18cd329dd754b4df5e0e2daece1e, 5.15.217, 0, <4.1, <83aa12f9f2468a4fbef027c09224dc1011850fb0, <dab741c9da72102a37cc1020a929051b7c45f9fb, <=7.1.*, <=5.10.*, <=6.6.*, 5.10.266, <=6.18.*, 6.1.184, 7.1.10, e831cd251fb91d6c25352d322743db0d17ea11dd, 4.1, <=*, <9da976eb649c9e2f588a4499410e4d8af687925f, <764b507be7b51787e1f577ca3bf0bab7efe81ff8, <=5.15.*, 6.6.153, 6.12.105, 6.18.46, <cd4ecce2fd87760c0ad9a9d28c9fc62ea1dbfd3d, 7.2, <beb9b0bd6e6e23f5e9e42b7ef890a50f57f1f3aa) 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