CVE-2026-45891

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 0, <6dc10494cfe27b6f1e9adb7e293293ae39c50b7c, 7.0, <fb6a4c376d454b425555b1b0bda36e99f56ec307, 6.1.165, 6.12.75, 907676b130711fd1f627824559e92259db2061d1, <6d2f142b1e4b203387a92519d9d2e34752a79dbb, <5.14, <=6.6.*, <d2c785733dfb853ea0b53984c75662a1af230a94, 5.14, <=6.19.*, <=6.18.*, 6.6.128, 6.19.4, <=*, <=5.15.*, <43015461662d41dcfb3bb95fadd8a2a42ad8eacf, 5.15.202, <fdbccddb7e7822016601829f95de4008e193f7bc, 6.18.14, <c3659273860bed0c8e573b865e3769abc51225a8

Description

In the Linux kernel, the following vulnerability has been resolved: net: hns3: fix double free issue for tx spare buffer In hns3_set_ringparam(), a temporary copy (tmp_rings) of the ring structure is created for rollback. However, the tx_spare pointer in the original ring handle is incorrectly left pointing to the old backup memory. Later, if memory allocation fails in hns3_init_all_ring() during the setup, the error path attempts to free all newly allocated rings. Since tx_spare contains a stale (non-NULL) pointer from the backup, it is mistaken for a newly allocated buffer and is erroneously freed, leading to a double-free of the backup memory. The root cause is that the tx_spare field was not cleared after its value was saved in tmp_rings, leaving a dangling pointer. Fix this by setting tx_spare to NULL in the original ring structure when the creation of the new `tx_spare` fails. This ensures the error cleanup path only frees genuinely newly allocated buffers.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 0, <6dc10494cfe27b6f1e9adb7e293293ae39c50b7c, 7.0, <fb6a4c376d454b425555b1b0bda36e99f56ec307, 6.1.165, 6.12.75, 907676b130711fd1f627824559e92259db2061d1, <6d2f142b1e4b203387a92519d9d2e34752a79dbb, <5.14, <=6.6.*, <d2c785733dfb853ea0b53984c75662a1af230a94, 5.14, <=6.19.*, <=6.18.*, 6.6.128, 6.19.4, <=*, <=5.15.*, <43015461662d41dcfb3bb95fadd8a2a42ad8eacf, 5.15.202, <fdbccddb7e7822016601829f95de4008e193f7bc, 6.18.14, <c3659273860bed0c8e573b865e3769abc51225a8) 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