Heimdall Security Logo

CVE-2026-23362

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

CVSS 0.0 · Non évaluée
EPSS 0.1%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, <800f26f11ae37b17f58e0001f28a47dd75c26557, <f0c349b2c21b220af5ba19f29b885e222958d796, 2a437b86ac5a9893c902f30ef66815bf13587bf6, 6.1.141, 0, 7595de7bc56e0e52b74e56c90f7e247bf626d628, 7.0, <5.15.203, <8215ba7bc99e84e66fd6938874ec4330a9d96518, 8f1c022541bf5a923c8d6fa483112c15250f30a4, c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7, 6.18.17, <70e951afad4c025261fe3c952d2b07237e320a01, 76c84c3728178b2d38d5604e399dfe8b0752645e, <5.10.253, 6.6.93, <c85b96eaf766d8f066b1139a17a51efa2f6627ef, <6.6.130, 6.14.9, 5.4.294, <=5.10.*, <=6.6.*, cc55dd28c20a6611e30596019b3b2f636819a4c0, fbd8fdc2b218e979cfe422b139b8f74c12419d1f, <=6.19.*, 5.15.203, <c35636e91e392e1540949bbc67932167cb48bc3a, <5.5, <6.12.77, <=6.18.*, 6.19.7, <6.1.167, 6.12.31, 6.1.167, 6.15, <=*, c4e8a172501e677ebd8ea9d9161d97dc4df56fbd, 5.10.253, <=5.15.*, <0904037e713f787d1376e1d349c3bdf6c3105881, 5.15.185, <6.15, <8bcf2d847adb82b2c617456f6da17ac5e6c75285, 6.12.77, 6.6.130, 5.10.238

Description

In the Linux kernel, the following vulnerability has been resolved: can: bcm: fix locking for bcm_op runtime updates Commit c2aba69d0c36 ("can: bcm: add locking for bcm_op runtime updates") added a locking for some variables that can be modified at runtime when updating the sending bcm_op with a new TX_SETUP command in bcm_tx_setup(). Usually the RX_SETUP only handles and filters incoming traffic with one exception: When the RX_RTR_FRAME flag is set a predefined CAN frame is sent when a specific RTR frame is received. Therefore the rx bcm_op uses bcm_can_tx() which uses the bcm_tx_lock that was only initialized in bcm_tx_setup(). Add the missing spin_lock_init() when allocating the bcm_op in bcm_rx_setup() to handle the RTR case properly.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, <800f26f11ae37b17f58e0001f28a47dd75c26557, <f0c349b2c21b220af5ba19f29b885e222958d796, 2a437b86ac5a9893c902f30ef66815bf13587bf6, 6.1.141, 0, 7595de7bc56e0e52b74e56c90f7e247bf626d628, 7.0, <5.15.203, <8215ba7bc99e84e66fd6938874ec4330a9d96518, 8f1c022541bf5a923c8d6fa483112c15250f30a4, c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7, 6.18.17, <70e951afad4c025261fe3c952d2b07237e320a01, 76c84c3728178b2d38d5604e399dfe8b0752645e, <5.10.253, 6.6.93, <c85b96eaf766d8f066b1139a17a51efa2f6627ef, <6.6.130, 6.14.9, 5.4.294, <=5.10.*, <=6.6.*, cc55dd28c20a6611e30596019b3b2f636819a4c0, fbd8fdc2b218e979cfe422b139b8f74c12419d1f, <=6.19.*, 5.15.203, <c35636e91e392e1540949bbc67932167cb48bc3a, <5.5, <6.12.77, <=6.18.*, 6.19.7, <6.1.167, 6.12.31, 6.1.167, 6.15, <=*, c4e8a172501e677ebd8ea9d9161d97dc4df56fbd, 5.10.253, <=5.15.*, <0904037e713f787d1376e1d349c3bdf6c3105881, 5.15.185, <6.15, <8bcf2d847adb82b2c617456f6da17ac5e6c75285, 6.12.77, 6.6.130, 5.10.238) 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