CVE-2026-64017

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

CVSS 7.8 · Élevée
EPSS 0.1%
Linux•Linux•Versions : <=7.0.*, 8b6075046470c8756242dfe3fd058813636f69a3, <=6.12.*, 33cf52b6e53a6aa55883aa7fb9ceffceff8488a6, 0, 6.5.13, 6.6.14, <388468f7e7d1eab092cf2a39fdfb502e52019ec6, 6.1.75, <6.6, <23d8ea1e303b5f32d883757a4a707e791dbc9808, b0077e269f6c152e807fdac90b58caf012cdbaab, 6.6.3, 7.1, <=6.18.*, 7.0.11, 6.12.104, <97e2d08de282ef76f84ab4ccd00f1acb3f5f999e, <6.2, b80056bd75a16e4550873ecefe12bc8fd190b1cf, <6.7, 6.18.45, <=*, <dc278e9bf2b9513a763353e6b9cc21e0f532954e, 6.1.72, 6.7, e9c309ded295b7f8849097d71ae231456ca79f78, b5c8e0ff76d10f6bf70a7237678f27c20cf59bc9

Description

In the Linux kernel, the following vulnerability has been resolved: blk-mq: pop cached request if it is usable When submitting a bio to blk-mq, if the task should sleep after peeking a cached request, but before it pops it, the plug flushes and calls blk_mq_free_plug_rqs, freeing the cached_rqs. This creates a use-after-free bug. Fix this by popping the cached request before any possible blocking calls if it is suitable for use. Popping this request first holds a queue reference, so avoid any serialization races with queue freezes and can safely proceed with dispatching that request to the driver. This potentially increases a timing window from when a driver wants to freeze its queue to when requests stop being dispatched. That scenario is off the fast path though, and drivers need to appropriately handle requests during a freeze request anyway. The downside is the popped element needs to be individually freed when we performed a bio plug merge. The cached request would have had to be freed later anyway, but this patch does it inline with building the plug list instead of after flushing it.

Gravité et risque d'exploitation

CVE-2026-64017 obtient un score CVSS de 7.8/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.13 %, ce qui la place devant 2.0 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=7.0.*, 8b6075046470c8756242dfe3fd058813636f69a3, <=6.12.*, 33cf52b6e53a6aa55883aa7fb9ceffceff8488a6, 0, 6.5.13, 6.6.14, <388468f7e7d1eab092cf2a39fdfb502e52019ec6, 6.1.75, <6.6, <23d8ea1e303b5f32d883757a4a707e791dbc9808, b0077e269f6c152e807fdac90b58caf012cdbaab, 6.6.3, 7.1, <=6.18.*, 7.0.11, 6.12.104, <97e2d08de282ef76f84ab4ccd00f1acb3f5f999e, <6.2, b80056bd75a16e4550873ecefe12bc8fd190b1cf, <6.7, 6.18.45, <=*, <dc278e9bf2b9513a763353e6b9cc21e0f532954e, 6.1.72, 6.7, e9c309ded295b7f8849097d71ae231456ca79f78, b5c8e0ff76d10f6bf70a7237678f27c20cf59bc9) 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