CVE-2026-64472

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

A fix is available — apply it.

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

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 17, 2026

References (6)

Vendor Advisories for CVE-2026-64472(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-15ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-15ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-15ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1—
linux-6.12—6.12.100-1~deb12u1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)6.12.100-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (158 versions)7.1.4-1—

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-15 09:19 UTCVendor advisory
  2. 2026-09-15 09:19 UTCGHSA enrichment
  3. 2026-09-12 06:55 UTCVendor advisory
  4. 2026-09-12 06:55 UTCGHSA enrichment
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-11 09:37 UTCEPSS rescore
  7. 2026-09-09 08:30 UTCVendor advisory
  8. 2026-09-09 08:30 UTCGHSA enrichment
  9. 2026-09-08 22:01 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-05 15:31 UTCEPSS rescore
  13. 2026-09-05 05:56 UTCGHSA enrichment
  14. 2026-09-04 05:07 UTCEPSS rescore
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 23:08 UTCGHSA enrichment
  17. 2026-09-01 13:54 UTCEPSS rescore
  18. 2026-09-01 04:40 UTCEPSS rescore
  19. 2026-08-30 19:17 UTCEPSS rescore
  20. 2026-08-30 01:22 UTCEPSS rescore
  21. 2026-08-30 00:02 UTCGHSA enrichment
  22. 2026-08-28 21:42 UTCEPSS rescore
  23. 2026-08-26 14:47 UTCEPSS rescore
  24. 2026-08-26 01:00 UTCGHSA enrichment
  25. 2026-08-25 13:49 UTCEPSS rescore
Show 50 more
  1. 2026-08-23 02:36 UTCGHSA enrichment
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 04:11 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-17 05:43 UTCGHSA enrichment
  10. 2026-08-17 05:25 UTCNVD update
  11. 2026-08-17 05:16 UTCGHSA enrichment
  12. 2026-08-17 05:05 UTCMITRE cvelistV5
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-15 15:41 UTCGHSA enrichment
  15. 2026-08-15 01:30 UTCEPSS rescore
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-12 17:15 UTCGHSA enrichment
  18. 2026-08-12 13:51 UTCEPSS rescore
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-09 18:50 UTCGHSA enrichment
  21. 2026-08-09 13:47 UTCEPSS rescore
  22. 2026-08-08 16:37 UTCEPSS rescore
  23. 2026-08-06 20:26 UTCGHSA enrichment
  24. 2026-08-06 13:47 UTCEPSS rescore
  25. 2026-08-05 19:17 UTCEPSS rescore
  26. 2026-08-05 19:17 UTCEPSS rescore
  27. 2026-08-04 15:10 UTCEPSS rescore
  28. 2026-08-04 10:39 UTCEPSS rescore
  29. 2026-08-03 22:02 UTCGHSA enrichment
  30. 2026-08-03 10:36 UTCEPSS rescore
  31. 2026-08-02 02:27 UTCEPSS rescore
  32. 2026-08-01 04:16 UTCEPSS rescore
  33. 2026-07-31 23:37 UTCEG score recompute
  34. 2026-07-31 23:37 UTCGHSA enrichment
  35. 2026-07-30 16:28 UTCEPSS rescore
  36. 2026-07-30 01:30 UTCEPSS rescore
  37. 2026-07-30 01:30 UTCEPSS rescore
  38. 2026-07-29 01:12 UTCEG score recompute
  39. 2026-07-29 01:12 UTCGHSA enrichment
  40. 2026-07-28 15:37 UTCEPSS rescore
  41. 2026-07-27 14:14 UTCEPSS rescore
  42. 2026-07-26 14:54 UTCEPSS rescore
  43. 2026-07-26 14:54 UTCEPSS rescore
  44. 2026-07-26 02:46 UTCEG score recompute
  45. 2026-07-26 02:46 UTCGHSA enrichment
  46. 2026-07-25 14:18 UTCEPSS rescore
  47. 2026-07-25 14:18 UTCEPSS rescore
  48. 2026-07-25 10:39 UTCNVD update
  49. 2026-07-25 09:26 UTCEG score recompute
  50. 2026-07-25 09:21 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-64472?
CVE-2026-64472 is a publicly disclosed vulnerability published on July 25, 2026. 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…
When was CVE-2026-64472 disclosed?
CVE-2026-64472 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64472 actively exploited?
CVE-2026-64472 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.2% of all scored CVEs.
How do I remediate CVE-2026-64472?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64472, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64472

Explore →

Is Your Infrastructure Affected by CVE-2026-64472?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs