Heimdall Security Logo

CVE-2026-72122

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

CVSS 7.3 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, 7.1.5, 6.18.40, <=6.12.*, 0, <=7.1.*, <ffa80a2af27c97453861a5128e537214a31cd18a, 6.1.178, <0f6f9f95294b4cbb26ba02209e893e3bd91237c3, <=5.10.*, <=6.6.*, 6.12.97, <6bcc5cd247c2934373bc2a1cdf8bf12321169543, <d9b091d9d22fee81ec53fb55d2032951993ceadb, <=6.18.*, 5.15.212, ffd980f976e7fd666c2e61bf8ab35107efd11828, 6.6.145, 5.10.261, 2.6.25, <b9c6ac6fb4e01b34575816066e5d3890a57b3c86, <2.6.25, <=*, <9e60c586faeaed80d55ab8ce2a4b8e56133bc395, <=5.15.*, <b70f1a15533afeeec5d07f20bec3f3867ab1c7b6, 7.2, <35f0ac19efb1a3f6c5e12c00e475a9ec2d9c3a6d

Description

In the Linux kernel, the following vulnerability has been resolved: can: bcm: fix lockless bound/ifindex race and silent RX_SETUP failure bcm_sendmsg() reads bo->ifindex and checks bo->bound before taking lock_sock(), while bcm_notify(), bcm_connect() and bcm_release() all mutate both fields under that same lock. Because the lockless reads and the locked writes are unordered with respect to each other, a racing bcm_notify() (device unregister) or bcm_connect() (concurrent bind on another thread sharing the socket) can make bcm_sendmsg() observe an inconsistent combination, e.g. a stale bound=1 together with the now-cleared ifindex=0, silently turning a socket bound to a specific CAN interface into one that also matches "any" interface. Keep the lockless bo->bound check purely as a fast-path reject, and move the ifindex read (and a bo->bound re-check) into the locked section, where every writer already serializes. This removes the possibility of observing the two fields torn against each other, rather than trying to fix it with more READ_ONCE()/WRITE_ONCE() pairs on two independently updated fields. Annotate the now-purely-lockless bo->bound accesses consistently across all its write sites. Also fix bcm_rx_setup() silently returning success when the target device disappears concurrently instead of reporting -ENODEV, so a broken RX op is no longer left registered as if it had succeeded.

Gravité et risque d'exploitation

CVE-2026-72122 obtient un score CVSS de 7.3/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.*, 0, <=7.1.*, <ffa80a2af27c97453861a5128e537214a31cd18a, 6.1.178, <0f6f9f95294b4cbb26ba02209e893e3bd91237c3, <=5.10.*, <=6.6.*, 6.12.97, <6bcc5cd247c2934373bc2a1cdf8bf12321169543, <d9b091d9d22fee81ec53fb55d2032951993ceadb, <=6.18.*, 5.15.212, ffd980f976e7fd666c2e61bf8ab35107efd11828, 6.6.145, 5.10.261, 2.6.25, <b9c6ac6fb4e01b34575816066e5d3890a57b3c86, <2.6.25, <=*, <9e60c586faeaed80d55ab8ce2a4b8e56133bc395, <=5.15.*, <b70f1a15533afeeec5d07f20bec3f3867ab1c7b6, 7.2, <35f0ac19efb1a3f6c5e12c00e475a9ec2d9c3a6d) 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