Heimdall Security Logo

CVE-2026-72125

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

CVSS 7.8 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, 7.1.5, 6.18.40, <=6.12.*, <43884dc7963beef2328f507f4fe680bdc173eb80, 6.12.101, <33b9cd9245e2a4b800f99ed1cc53d64960614152, e057dd3fc20ffb3d7f150af46542a51b59b90127, 0, <8e018f4335590460ebcf0c2b493ed38ba1a35204, <=7.1.*, <0b811c4bbe3ec9ad611e90a540fe8b51b3bb8a96, 5.15.216, <=5.10.*, <=6.6.*, <e442b62ba5a7756c17e05a77b32cdd085a2b6138, <7bef39ba76eb7307ed22a50329e0f5776dbeda58, 6.1.183, <5.10, <=6.18.*, <=*, <=5.15.*, <20bab8b88baac140ca3701116e1d486c7f51e311, <f311bbb29bb06aaab69ba45a6e4b11323d20b8f9, 5.10.265, 6.6.148, 7.2, 5.10

Description

In the Linux kernel, the following vulnerability has been resolved: can: isotp: fix use-after-free race with concurrent NETDEV_UNREGISTER isotp_release() looked up the bound network device via dev_get_by_index() using the stored ifindex. During device unregistration the device is unlisted from the ifindex hash before the NETDEV_UNREGISTER notifier chain runs, so a concurrent isotp_release() could find no device, skip can_rx_unregister() entirely, and still proceed to free the socket. Since isotp_release() had already removed itself from the isotp notifier list at that point, isotp_notify() would never get a chance to clean up either, leaving a stale CAN filter that keeps pointing at the freed socket. Fix this the same way raw.c already does: hold a tracked reference to the bound net_device in the socket (so->dev/so->dev_tracker) from bind() onward instead of re-resolving it from the ifindex, and serialize bind()/release() with rtnl_lock() so that so->dev is always consistent with what the NETDEV_UNREGISTER notifier sees. so->dev stays valid regardless of ifindex-hash unlisting, and is only ever cleared by whichever of isotp_release()/isotp_notify() gets there first, so the filter is always removed exactly once. isotp_bind() now rejects a (re)bind with -EAGAIN while so->[tx|rx].state isn't ISOTP_IDLE yet, so a timer left running by a prior NETDEV_UNREGISTER can't act on a newly bound so->ifindex. Both checks share the same lock_sock() section, so there is no window in which a concurrent isotp_notify() clearing so->bound could be missed.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, 7.1.5, 6.18.40, <=6.12.*, <43884dc7963beef2328f507f4fe680bdc173eb80, 6.12.101, <33b9cd9245e2a4b800f99ed1cc53d64960614152, e057dd3fc20ffb3d7f150af46542a51b59b90127, 0, <8e018f4335590460ebcf0c2b493ed38ba1a35204, <=7.1.*, <0b811c4bbe3ec9ad611e90a540fe8b51b3bb8a96, 5.15.216, <=5.10.*, <=6.6.*, <e442b62ba5a7756c17e05a77b32cdd085a2b6138, <7bef39ba76eb7307ed22a50329e0f5776dbeda58, 6.1.183, <5.10, <=6.18.*, <=*, <=5.15.*, <20bab8b88baac140ca3701116e1d486c7f51e311, <f311bbb29bb06aaab69ba45a6e4b11323d20b8f9, 5.10.265, 6.6.148, 7.2, 5.10) 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