CVE-2026-64472

Description

In the Linux kernel, the following vulnerability has been resolved: vfio/mlx5: Fix racy bitfields and tighten struct layout Bitfield operations are not atomic, they use a read-modify-write pattern, therefore we should be careful not to pack bitfields that can be concurrently updated into the same storage unit. This split takes a binary approach: flags that are only modified pre/post open/close remain bitfields, flags modified from user action, including actions that reach across to another device (ex. reset) use dedicated storage units. Note mlx5_vhca_page_tracker.status is relocated to fill the alignment hole this split exposes. Bitfield justifications: migrate_cap: written only in mlx5vf_cmd_set_migratable() at probe chunk_mode: written only in mlx5vf_cmd_set_migratable() at probe mig_state_cap: written only in mlx5vf_cmd_set_migratable() at probe Dedicated storage units: mdev_detach: written in the VF attach/detach event notifier mlx5fv_vf_event() at runtime log_active: written in mlx5vf_start_page_tracker()/ mlx5vf_stop_page_tracker() during runtime dirty tracking deferred_reset: written in mlx5vf_state_mutex_unlock()/ mlx5vf_pci_aer_reset_done() during runtime reset handling is_err: set by tracker error handling and dirty-log polling at runtime object_changed: set by tracker event handling and cleared by dirty-log polling at runtime

Gravité et risque d'exploitation

CVE-2026-64472 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 7.2 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions <f2365a63b02ddea32e7db78b742c2503ec7b81f1, <=6.1.*, 6.18.40, <=6.12.*, 61a2f1460fd03285ea34c1a235f2f50f71e13a1f, <39d163627b51886492bf31f66cb02c94613d2287, 0, <=7.1.*, 7.1.4, 5.19, <f1db80a67da928a92ba460ede1be52d8941f46be, 6.1.178, 6.12.97, <=6.6.*, <7ed120b1a007bace57c461805519d70e1af44e59, <=6.18.*, 6.6.145, <5.19, <1dd99b8f4e143592e12e5a77e7b538bc698116cb, <=*, <399d806f998f7a25405fc1b97227e579aead24af, 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

• https://git.kernel.org/stable/c/1dd99b8f4e143592e12e5a77e7b538bc698116cb
• https://git.kernel.org/stable/c/f1db80a67da928a92ba460ede1be52d8941f46be
• https://git.kernel.org/stable/c/399d806f998f7a25405fc1b97227e579aead24af
• https://git.kernel.org/stable/c/7ed120b1a007bace57c461805519d70e1af44e59
• https://git.kernel.org/stable/c/39d163627b51886492bf31f66cb02c94613d2287
• https://git.kernel.org/stable/c/f2365a63b02ddea32e7db78b742c2503ec7b81f1