Heimdall Security Logo

CVE-2026-23103

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

CVSS 7.8 · Élevée
EPSS 0.1%
Linux•Linux•Versions : <88f83e6c9cdb46b8c8ddd0ba01393362963cf589, <=6.1.*, <=6.12.*, 0, <6a81e2db096913d7e43aada1c350c1282e76db39, 5.15.199, <4.17, 8230819494b3bf284ca7262ac5f877333147b937, <=5.10.*, <=6.6.*, 5.10.249, 6.18.8, 4.17, 6.1.162, <=6.18.*, <3c149b662cbb202a450e81f938e702ba333864ad, 6.12.68, <70feb16e3fbfb10b15de1396557c38e99f1ab8df, <=*, <=5.15.*, 6.19, <1f300c10d92c547c3a7d978e1212ff52f18256ed, <04ba6de6eff61238e5397c14ac26a6578c7735a5, 6.6.122, <d3ba32162488283c0a4c5bedd8817aec91748802

Description

In the Linux kernel, the following vulnerability has been resolved: ipvlan: Make the addrs_lock be per port Make the addrs_lock be per port, not per ipvlan dev. Initial code seems to be written in the assumption, that any address change must occur under RTNL. But it is not so for the case of IPv6. So 1) Introduce per-port addrs_lock. 2) It was needed to fix places where it was forgotten to take lock (ipvlan_open/ipvlan_close) This appears to be a very minor problem though. Since it's highly unlikely that ipvlan_add_addr() will be called on 2 CPU simultaneously. But nevertheless, this could cause: 1) False-negative of ipvlan_addr_busy(): one interface iterated through all port->ipvlans + ipvlan->addrs under some ipvlan spinlock, and another added IP under its own lock. Though this is only possible for IPv6, since looks like only ipvlan_addr6_event() can be called without rtnl_lock. 2) Race since ipvlan_ht_addr_add(port) is called under different ipvlan->addrs_lock locks This should not affect performance, since add/remove IP is a rare situation and spinlock is not taken on fast paths.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <88f83e6c9cdb46b8c8ddd0ba01393362963cf589, <=6.1.*, <=6.12.*, 0, <6a81e2db096913d7e43aada1c350c1282e76db39, 5.15.199, <4.17, 8230819494b3bf284ca7262ac5f877333147b937, <=5.10.*, <=6.6.*, 5.10.249, 6.18.8, 4.17, 6.1.162, <=6.18.*, <3c149b662cbb202a450e81f938e702ba333864ad, 6.12.68, <70feb16e3fbfb10b15de1396557c38e99f1ab8df, <=*, <=5.15.*, 6.19, <1f300c10d92c547c3a7d978e1212ff52f18256ed, <04ba6de6eff61238e5397c14ac26a6578c7735a5, 6.6.122, <d3ba32162488283c0a4c5bedd8817aec91748802) 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