CVE-2026-64473

In the Linux kernel, the following vulnerability has been resolved: vfio: Remove device debugfs before releasing devres VFIO device debugfs files created with debugfs_create_devm_seqfile() store a devres allocated debugfs_devm_entry as inode private data. vfio_unregister_group_dev() currently calls vfio_device_del() before vfio_device_debugfs_exit(), but device_del() releases devres. This can leave debugfs entries visible with stale inode private data while unregister waits for userspace references to drain. Remove the per-device debugfs tree before vfio_device_del(). The debugfs view is diagnostic only, so losing it at the start of unregister is preferable to preserving entries whose backing storage may already have been released. Complete the teardown by clearing the per-device debugfs root after removal. This matches the global debugfs root cleanup and prevents future users from mistaking a removed dentry for a live debugfs tree during the remainder of unregister.

Package Linux Kernel
Published 2026-07-25
Last modified 2026-07-25
Patch available
Yes

Affected versions

Linux kernel versions 6.8 and later are affected. Fixed in 6.12.96, 6.18.39, 7.1.4, 7.2-rc2 and their respective stable series.

Affected from
≥ 6.8
Fixed in
✓ 6.12.96 6.12.x ✓ 6.18.39 6.18.x ✓ 7.1.4 7.1.x ✓ 7.2-rc2

Frequently asked questions

  • What is CVE-2026-64473?

    CVE-2026-64473 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 6.8 onward and has been patched in 6.12.96, 6.18.39, 7.1.4 and others. CVE-2026-64473 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • Is there a patch available for CVE-2026-64473?

    Yes. CVE-2026-64473 has been patched. Fixed versions include 6.12.96, 6.18.39, 7.1.4 and others. If you are running Linux kernel 6.8 or later up to the fix versions, apply the relevant patch for your kernel branch.

  • Is CVE-2026-64473 actively exploited?

    No. CVE-2026-64473 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.