Skip to main content
VulnerabilityPublished Updated

CVE-2026-64473: Linux kernel · vfio: Remove device debugfs before releasing devres

Affects Linux kernelSource GCVE Database

0
Compare

Not known to be exploited.

Data as of 3 Nov 2026, 19:29 UTC

Severity
Low

Rated Low by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

What to do

AI-suggested

A fix has been implemented in the Linux kernel to remove the per-device debugfs tree before releasing device resources and to clear the debugfs root after removal. Users should update to the fixed kernel version once available. No additional mitigation is required as the debugfs view is diagnostic only and the issue does not pose a direct security risk.

Description

A vulnerability in the Linux kernel's VFIO subsystem involves improper removal of device debugfs entries during device unregistration. Debugfs entries created for VFIO devices may remain visible with stale inode private data after device resources are released, potentially causing confusion or diagnostic inaccuracies. The fix involves removing the per-device debugfs tree before releasing device resources and clearing the debugfs root to prevent stale entries.

References

Community reviews

Loading reviews…