CVE-2026-64473

published

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.

Technical severity5.5 mediumCVSS 3.1 · NVD: [email protected]

Published2026-07-25Source updated 2026-11-12

Collected2026-11-122 attributed sources

Fixes and workarounds

Fix

The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.

Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Fix

The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.

Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Fix

The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.

Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Fix

The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.

Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Affected products and versions

Affected products, source version ranges and reporting authorities
Product	Versions	Authority
linux_kernel linux	≥ 6.8; < 6.12.96 (affected, custom)	NVD
linux_kernel linux	≥ 6.13; < 6.18.39 (affected, custom)	NVD
linux_kernel linux	≥ 6.19; < 7.1.4 (affected, custom)	NVD
linux_kernel linux	7.2 (affected, custom)	NVD

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

NVD applicability configurations (1)

These expressions retain AND/OR operators, negation, and required environmental products. A listed product is not sufficient to establish exposure when additional conditions apply.

[
  {
    "negate": false,
    "nodes": [
      {
        "cpeMatch": [
          {
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionEndExcluding": "6.12.96",
            "versionStartIncluding": "6.8",
            "vulnerable": true
          },
          {
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionEndExcluding": "6.18.39",
            "versionStartIncluding": "6.13",
            "vulnerable": true
          },
          {
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionEndExcluding": "7.1.4",
            "versionStartIncluding": "6.19",
            "vulnerable": true
          },
          {
            "criteria": "cpe:2.3:o:linux:linux_kernel:7.2:rc1:*:*:*:*:*:*",
            "vulnerable": true
          }
        ],
        "negate": false,
        "operator": "OR"
      }
    ],
    "operator": "OR"
  }
]

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / score	Vector	Authority
3.1 / 5.5 medium	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`	NVD: [email protected]

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

https://git.kernel.org/stable/c/6cc60b41d61657dc469893d14e8e55d160056ff1416baaa9-dc9f-4396-8d5f-8c081fb06d67 · Patch
https://git.kernel.org/stable/c/a53109ffb6b5148e11a27fb7670355b92db12dd3416baaa9-dc9f-4396-8d5f-8c081fb06d67 · Patch
https://git.kernel.org/stable/c/a5df401dc84f091e20b045560569f0736758fea7416baaa9-dc9f-4396-8d5f-8c081fb06d67 · Patch
https://git.kernel.org/stable/c/dc7fe87de492ea7f33a72b78d26650b75bf37f4f416baaa9-dc9f-4396-8d5f-8c081fb06d67 · Patch

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Get an API key Use x402 Connect an agent

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide