Heimdall Security Logo

CVE-2026-89741

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

CVSS 7.8 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <6.6.157, <=6.1.*, <=6.12.*, <5.15.221, b6be1f5633eae200af2527e9eeb7f51be5739b0f, 5.15.221, <6.12.109, <712ca1cf756de2557a116e0df55791bac0c9f99e, 0, 5.10.270, 7.2.4, <ce792b94e03882108019ba996c1a7c4d4e09be2c, 8b451a9a46f2bfc510e6d5c2492df91647586184, 6.1.188, <aad08b5f67d2a8116e1a00bce2611c1513b10bce, ae7b143e05b36fc69d6571751855946cc45064c6, 5.4.295, 5.15.186, <=5.10.*, <=6.6.*, 6.1.142, 4451412739ed33a49b34624299394ee575116d0c, 5.10.239, e5c8e62ae551e0ad2e15412aa0c57c2856d59677, 6.6.157, 2429bb9fad88c8fa84c4956b0a21cf5afe5e92b7, <3de14b4f681a1b3c6d375d98d9d37a55ebb85349, 6.16, <5.5, <=6.18.*, <5.10.270, <=7.2.*, 6.12.35, <2ac009a65d2385e9f0799eaf9d9694a29153a161, <6.16, <=*, <=5.15.*, 6.15.4, <8b998c171ed875e402e1fd1c5cd619e4ca05e9c1, 2a934fdb01db6458288fc9386d3d8ceba6dd551a, <8027f82c0f5474ed72448e160ee9778051fa1f49, 6.18.50, 6.6.95, <6.1.188, 6.12.109, <e7600f5cee5de14065f950807931d6e6d40fb2d7, ee141706e701356dda41c6fed9ee18bf427c28e3, 7.3

Description

In the Linux kernel, the following vulnerability has been resolved: Revert "media: v4l2-dev: fix error handling in __video_register_device()" This reverts commit 2a934fdb01db6458288fc9386d3d8ceba6dd551a. The intentions of that patch were good, but it doesn't work. The idea is that if device_register fails, you have to do a put_device to let the ref counter release resources. However, the V4L2 API says that if video_register_device() fails, then you have to call video_device_release(), which kfree()s the video_device struct. But the put_device() will already have freed the struct, so you end up in a double-free scenario. There is not really a good way of fixing this without breaking video_register_device() into two parts, one that initializes everything, and one that does the actual device_register, and then converting all V4L2 drivers to this new model. That is a massive job, and it is very unlikely that device_register will fail. So rather than ending up in a double-free scenario, just revert this patch, and in that case we'll have a small memory leak. Which is a lot more robust.

Gravité et risque d'exploitation

CVE-2026-89741 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.17 %, ce qui la place devant 5.8 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <6.6.157, <=6.1.*, <=6.12.*, <5.15.221, b6be1f5633eae200af2527e9eeb7f51be5739b0f, 5.15.221, <6.12.109, <712ca1cf756de2557a116e0df55791bac0c9f99e, 0, 5.10.270, 7.2.4, <ce792b94e03882108019ba996c1a7c4d4e09be2c, 8b451a9a46f2bfc510e6d5c2492df91647586184, 6.1.188, <aad08b5f67d2a8116e1a00bce2611c1513b10bce, ae7b143e05b36fc69d6571751855946cc45064c6, 5.4.295, 5.15.186, <=5.10.*, <=6.6.*, 6.1.142, 4451412739ed33a49b34624299394ee575116d0c, 5.10.239, e5c8e62ae551e0ad2e15412aa0c57c2856d59677, 6.6.157, 2429bb9fad88c8fa84c4956b0a21cf5afe5e92b7, <3de14b4f681a1b3c6d375d98d9d37a55ebb85349, 6.16, <5.5, <=6.18.*, <5.10.270, <=7.2.*, 6.12.35, <2ac009a65d2385e9f0799eaf9d9694a29153a161, <6.16, <=*, <=5.15.*, 6.15.4, <8b998c171ed875e402e1fd1c5cd619e4ca05e9c1, 2a934fdb01db6458288fc9386d3d8ceba6dd551a, <8027f82c0f5474ed72448e160ee9778051fa1f49, 6.18.50, 6.6.95, <6.1.188, 6.12.109, <e7600f5cee5de14065f950807931d6e6d40fb2d7, ee141706e701356dda41c6fed9ee18bf427c28e3, 7.3) 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