CVE-2026-46165

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

CVSS 0.0 · Non évaluée
EPSS 0.1%
Linux•Linux•Versions : <=6.1.*, 7.0.7, <=7.0.*, <=6.12.*, 98b726ab5e2a4811e27c28e4d041f75bba147eab, <366c482965c673565ecb8bcfb15d5548f13a6a10, b8c56a3fc5d879c0928f207a756b0f067f06c6a8, 0, <8ae6c15fc473c9ad03b0173330cce9a092c76154, 7.0, 9d56aced21fb9c104e8a3f3be9b21fbafe448ffc, <3df75fff46b1517eb479d8e6b8e3500763715dd0, <aa69918bd418e700309fdd08509dba324fb24296, bbe7bd722bfaea36aab3da6cc60fb4a05c644643, 6.12.88, <=6.6.*, 6.1.175, 6.19.11, <7.0, <6.20, 7.1, <=6.18.*, 6.6.131, 6931d21f87bc6d657f145798fad0bf077b82486c, <6.18.30, 6.12.80, <6.6.140, <=*, <6522d59fb7de55ce0f0f285d962243ddffebb01f, 6.1.168, 42f0d3d81209654c08ffdde5a34b9b92d2645896, <6.1.175, 6.6.140, 6.18.30, 6.18.21, <c741433f6c8dcdecd1d9549d89053761fd1ea413, <6.12.88

Description

In the Linux kernel, the following vulnerability has been resolved: openvswitch: vport: fix self-deadlock on release of tunnel ports vports are used concurrently and protected by RCU, so netdev_put() must happen after the RCU grace period. So, either in an RCU call or after the synchronize_net(). The rtnl_delete_link() must happen under RTNL and so can't be executed in RCU context. Calling synchronize_net() while holding RTNL is not a good idea for performance and system stability under load in general, so calling netdev_put() in RCU call is the right solution here. However, when the device is deleted, rtnl_unlock() will call netdev_run_todo() and block until all the references are gone. In the current code this means that we never reach the call_rcu() and the vport is never freed and the reference is never released, causing a self-deadlock on device removal. Fix that by moving the rcu_call() before the rtnl_unlock(), so the scheduled RCU callback will be executed when synchronize_net() is called from the rtnl_unlock()->netdev_run_todo() while the RTNL itself is already released.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, 7.0.7, <=7.0.*, <=6.12.*, 98b726ab5e2a4811e27c28e4d041f75bba147eab, <366c482965c673565ecb8bcfb15d5548f13a6a10, b8c56a3fc5d879c0928f207a756b0f067f06c6a8, 0, <8ae6c15fc473c9ad03b0173330cce9a092c76154, 7.0, 9d56aced21fb9c104e8a3f3be9b21fbafe448ffc, <3df75fff46b1517eb479d8e6b8e3500763715dd0, <aa69918bd418e700309fdd08509dba324fb24296, bbe7bd722bfaea36aab3da6cc60fb4a05c644643, 6.12.88, <=6.6.*, 6.1.175, 6.19.11, <7.0, <6.20, 7.1, <=6.18.*, 6.6.131, 6931d21f87bc6d657f145798fad0bf077b82486c, <6.18.30, 6.12.80, <6.6.140, <=*, <6522d59fb7de55ce0f0f285d962243ddffebb01f, 6.1.168, 42f0d3d81209654c08ffdde5a34b9b92d2645896, <6.1.175, 6.6.140, 6.18.30, 6.18.21, <c741433f6c8dcdecd1d9549d89053761fd1ea413, <6.12.88) 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