CVE-2026-43189

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.12.*, <461733d83e67ba7e3a5b750c0d203f738e01244f, 28a1295795d85a25f2e7dd391c43969e95fcb341, 0, 7.0, 6.12.75, <6.6, <b02bcb378efa8af07827f49b3afcc5e825318c55, <=6.6.*, <2de0a3c8148fc3dbea21981e6569f550b3626119, <=6.19.*, 6.6, <30aaed311f973f13ba13a0cd2dc0202f595fff48, <=6.18.*, 6.19.6, 6.6.128, 6.18.16, <=*, <7345d6d356336c448d6b9230ed8704f39679fd12

Description

In the Linux kernel, the following vulnerability has been resolved: media: v4l2-async: Fix error handling on steps after finding a match Once an async connection is found to be matching with an fwnode, a sub-device may be registered (in case it wasn't already), its bound operation is called, ancillary links are created, the async connection is added to the sub-device's list of connections and removed from the global waiting connection list. Further on, the sub-device's possible own notifier is searched for possible additional matches. Fix these specific issues: - If v4l2_async_match_notify() failed before the sub-notifier handling, the async connection was unbound and its entry removed from the sub-device's async connection list. The latter part was also done in v4l2_async_match_notify(). - The async connection's sd field was only set after creating ancillary links in v4l2_async_match_notify(). It was however dereferenced in v4l2_async_unbind_subdev_one(), which was called on error path of v4l2_async_match_notify() failure.

Gravité et risque d'exploitation

CVE-2026-43189 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.0 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.12.*, <461733d83e67ba7e3a5b750c0d203f738e01244f, 28a1295795d85a25f2e7dd391c43969e95fcb341, 0, 7.0, 6.12.75, <6.6, <b02bcb378efa8af07827f49b3afcc5e825318c55, <=6.6.*, <2de0a3c8148fc3dbea21981e6569f550b3626119, <=6.19.*, 6.6, <30aaed311f973f13ba13a0cd2dc0202f595fff48, <=6.18.*, 6.19.6, 6.6.128, 6.18.16, <=*, <7345d6d356336c448d6b9230ed8704f39679fd12) 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