Heimdall Security Logo

CVE-2026-72115

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

CVSS 8.1 · Élevée
EPSS 0.3%
Linux•Linux•Versions : <=6.1.*, 7.1.5, <=6.12.*, 6.12.101, 0, <=7.1.*, <3ff8c24b421070a2db99a5cdb86edc9ff339418e, 5.15.216, <18b45251e74e35668f0dd0c470549384ae191ecf, <=5.10.*, <=6.6.*, <b6317022b685a430a3ae420456716e3c0c02ef4b, 6.18.42, <2f5976f54a04e9f18b25283036ac3136be453b17, <f147f48837cb1426521f5b3c3b3134c71128a25d, <03dfe347c398fa41a7e30e8dc538f12568c183e6, 6.1.183, <57cf104da4cf450ae9c16801a3164604b801d2cc, <=6.18.*, ffd980f976e7fd666c2e61bf8ab35107efd11828, 2.6.25, <2.6.25, <=*, <=5.15.*, <eca8b44d51fc6ab61022258ec968e55e3073b79e, 5.10.265, 6.6.148, 7.2

Description

In the Linux kernel, the following vulnerability has been resolved: can: bcm: track a single source interface for ANYDEV timeout/throttle ops An ANYDEV rx op (ifindex == 0) with an active RX timeout and/or throttle timer has no defined semantics when matching frames arrive from several interfaces: bcm_rx_handler() can run concurrently for the same op on different CPUs, racing hrtimer_cancel()/ bcm_rx_starttimer() against bcm_rx_timeout_handler() and causing spurious RX_TIMEOUT notifications and last_frames corruption. The same concurrency lets throttled multiplex frames from different interfaces clobber the single rx_ifindex/rx_stamp fields shared by the op. Add op->if_detected to track the first interface that delivers a matching frame while a timeout/throttle timer is configured, and reject frames from any other interface for that op. The claim is decided in bcm_rx_handler() before hrtimer_cancel() touches op->timer, so a rejected frame can never disturb the claimed interface's watchdog. RTR-mode ops are excluded via RX_RTR_FRAME, independent of kt_ival1/kt_ival2, since those may briefly hold a stale value from an earlier non-RTR configuration. The claim is released in bcm_notify() on NETDEV_UNREGISTER and in bcm_rx_setup() when SETTIMER reconfigures the timer values. A (re-)claim is only possible on CAN devices in NETREG_REGISTERED dev->reg_state to cover the release in bcm_notify() where reg_state becomes NETREG_UNREGISTERING until synchronize_net().

Gravité et risque d'exploitation

CVE-2026-72115 obtient un score CVSS de 8.1/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.30 %, ce qui la place devant 21.6 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, 7.1.5, <=6.12.*, 6.12.101, 0, <=7.1.*, <3ff8c24b421070a2db99a5cdb86edc9ff339418e, 5.15.216, <18b45251e74e35668f0dd0c470549384ae191ecf, <=5.10.*, <=6.6.*, <b6317022b685a430a3ae420456716e3c0c02ef4b, 6.18.42, <2f5976f54a04e9f18b25283036ac3136be453b17, <f147f48837cb1426521f5b3c3b3134c71128a25d, <03dfe347c398fa41a7e30e8dc538f12568c183e6, 6.1.183, <57cf104da4cf450ae9c16801a3164604b801d2cc, <=6.18.*, ffd980f976e7fd666c2e61bf8ab35107efd11828, 2.6.25, <2.6.25, <=*, <=5.15.*, <eca8b44d51fc6ab61022258ec968e55e3073b79e, 5.10.265, 6.6.148, 7.2) 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