CVE-2026-64472
vfio/mlx5: Fix racy bitfields and tighten struct layout
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
INFO
Published Date :
July 25, 2026, 10:17 a.m.
Last Modified :
July 25, 2026, 10:17 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-64472
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Separate bitfields modified concurrently.
- Use dedicated storage for runtime-modified flags.
- Update affected structures and ensure proper alignment.
- Apply provided kernel patches or updates.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-64472.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-64472 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-64472
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-64472 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-64472 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 25, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '61a2f1460fd03285ea34c1a235f2f50f71e13a1f', 'lessThan': '1dd99b8f4e143592e12e5a77e7b538bc698116cb', 'versionType': 'git'}, {'status': 'affected', 'version': '61a2f1460fd03285ea34c1a235f2f50f71e13a1f', 'lessThan': 'f1db80a67da928a92ba460ede1be52d8941f46be', 'versionType': 'git'}, {'status': 'affected', 'version': '61a2f1460fd03285ea34c1a235f2f50f71e13a1f', 'lessThan': '399d806f998f7a25405fc1b97227e579aead24af', 'versionType': 'git'}, {'status': 'affected', 'version': '61a2f1460fd03285ea34c1a235f2f50f71e13a1f', 'lessThan': '7ed120b1a007bace57c461805519d70e1af44e59', 'versionType': 'git'}, {'status': 'affected', 'version': '61a2f1460fd03285ea34c1a235f2f50f71e13a1f', 'lessThan': '39d163627b51886492bf31f66cb02c94613d2287', 'versionType': 'git'}, {'status': 'affected', 'version': '61a2f1460fd03285ea34c1a235f2f50f71e13a1f', 'lessThan': 'f2365a63b02ddea32e7db78b742c2503ec7b81f1', 'versionType': 'git'}], 'programFiles': ['drivers/vfio/pci/mlx5/cmd.h'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '5.19'}, {'status': 'unaffected', 'version': '0', 'lessThan': '5.19', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.1.178', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.145', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.97', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.40', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.4', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc2', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/vfio/pci/mlx5/cmd.h'], 'defaultStatus': 'affected'}] Added 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 Added Reference https://git.kernel.org/stable/c/1dd99b8f4e143592e12e5a77e7b538bc698116cb Added Reference https://git.kernel.org/stable/c/399d806f998f7a25405fc1b97227e579aead24af Added Reference https://git.kernel.org/stable/c/39d163627b51886492bf31f66cb02c94613d2287 Added Reference https://git.kernel.org/stable/c/7ed120b1a007bace57c461805519d70e1af44e59 Added Reference https://git.kernel.org/stable/c/f1db80a67da928a92ba460ede1be52d8941f46be Added Reference https://git.kernel.org/stable/c/f2365a63b02ddea32e7db78b742c2503ec7b81f1