CVE-2026-72070

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, 7.1.5, 6.18.40, <=6.12.*, 6.12.101, 5.15.217, 0, <=7.1.*, 2.6.28, <fcff712d0e3d183843ec3916470ee6cc3455baad, <=5.10.*, <=6.6.*, <4714e95f5d61cb9c5c7c6c4e68b618f37bc6ffcf, <9392fd5de555272449d3d8c63410ea00f8ec853a, 5.10.266, <bd75636681588c67006279abdb9a76a708b3ce29, 06b16ae5319251c26377afcb401e46056d5673f4, <2.6.28, <aa6dcd5c8dd9ba1d7d0f60093bcda41c0d6d438d, <=6.18.*, 6.1.184, <2fba1d3b2f031a2c68e566a6d45cc5b7a8d6683d, <=*, <bcf7968cb97ce4312588042cf2712f04caff6d8f, <=5.15.*, <066b59e84f90d270cc15f0370166155aca507630, 6.6.148, 7.2

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: libertas_tf: fix use-after-free in lbtf_free_adapter() lbtf_free_adapter() calls timer_delete(&priv->command_timer), which does not wait for a running command_timer_fn() callback. lbtf_free_adapter() runs on the teardown path right before ieee80211_free_hw() frees priv, both in lbtf_remove_card() and in the probe error path. command_timer is armed by mod_timer() in lbtf_cmd() whenever a firmware command is sent. command_timer_fn() dereferences priv. If a command times out as the device is removed, command_timer_fn() runs concurrently with teardown and dereferences priv after it has been freed. This is the same use-after-free that commit 03cc8f90d053 ("wifi: libertas: fix use-after-free in lbs_free_adapter()") fixed in the sibling libertas driver. The libertas_tf variant has the identical pattern and was left unchanged. Use timer_delete_sync() so any in-flight callback completes before priv is freed.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, 7.1.5, 6.18.40, <=6.12.*, 6.12.101, 5.15.217, 0, <=7.1.*, 2.6.28, <fcff712d0e3d183843ec3916470ee6cc3455baad, <=5.10.*, <=6.6.*, <4714e95f5d61cb9c5c7c6c4e68b618f37bc6ffcf, <9392fd5de555272449d3d8c63410ea00f8ec853a, 5.10.266, <bd75636681588c67006279abdb9a76a708b3ce29, 06b16ae5319251c26377afcb401e46056d5673f4, <2.6.28, <aa6dcd5c8dd9ba1d7d0f60093bcda41c0d6d438d, <=6.18.*, 6.1.184, <2fba1d3b2f031a2c68e566a6d45cc5b7a8d6683d, <=*, <bcf7968cb97ce4312588042cf2712f04caff6d8f, <=5.15.*, <066b59e84f90d270cc15f0370166155aca507630, 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