CVE-2026-64472

CVE CVE-2026-64472EUVD EUVD-2026-48816Published 2026-07-25T08:51:35.000Z

What the advisory describes

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

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 61a2f1460fd03285ea34c1a235f2f50f71e13a1f <7ed120b1a007bace57c461805519d70e1af44e59; patch: 0; patch: 7.1.4; patch: 6.18.40; patch: 6.12.97; patch: 7.2-rc2; 61a2f1460fd03285ea34c1a235f2f50f71e13a1f <39d163627b51886492bf31f66cb02c94613d2287; 61a2f1460fd03285ea34c1a235f2f50f71e13a1f <1dd99b8f4e143592e12e5a77e7b538bc698116cb; patch: 6.1.178; patch: 6.6.145; 5.19; 61a2f1460fd03285ea34c1a235f2f50f71e13a1f <f2365a63b02ddea32e7db78b742c2503ec7b81f1; 61a2f1460fd03285ea34c1a235f2f50f71e13a1f <399d806f998f7a25405fc1b97227e579aead24af; 61a2f1460fd03285ea34c1a235f2f50f71e13a1f <f1db80a67da928a92ba460ede1be52d8941f46be

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.