CVE-2026-64475 — vfio/pci: Release the VGA arbiter client on register_device() failure
In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Release the VGA arbiter client on register_device() failure The re-order in the Fixes commit below displaced vfio_pci_vga_init() as the last failure point of what is now vfio_pci_core_register_device() without introducing an unwind for the VGA arbiter registration. In current kernels this is mostly benign because vfio_pci_set_decode() only uses pci_dev state, but the original failure path could leave a callback with a freed vdev cookie. The stale registration also becomes unsafe again once the callback follows drvdata to the vfio device. Add the required VGA unwind callout.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 87856f9af04eaacf9848710625a4ffee1d020fa9 and < 0f2a35a0c7ea7da347b814750eaa78adf3582381≥ 4aeec3984ddc853f7c65903bde472ffdef738bae and < 8d65decde9afd2bd78bcfffdc0df73b82a0b5509≥ 4aeec3984ddc853f7c65903bde472ffdef738bae and < ef4c38d30b3744e89eb5048218904bb629ea8d47≥ 4aeec3984ddc853f7c65903bde472ffdef738bae and < 9e0a3f642e607848669235f5069f35640abbfc88≥ 4aeec3984ddc853f7c65903bde472ffdef738bae and < 42d758a09d2c46c42357ecde9a5492f015bde2e5≥ 4aeec3984ddc853f7c65903bde472ffdef738bae and < 52adb2dff7ce3d8430e2bdc5988b618a430def85≥ 4aeec3984ddc853f7c65903bde472ffdef738bae and < 278a5659c391fe5afe5f9ce1bad1fd24e90144f1≥ 4aeec3984ddc853f7c65903bde472ffdef738bae and < daedde7f024ecf88bc8e832ed40cf2c795f0796a and 6 moreversion d62dccb417cf972c978bf3c68a7d5e846bcf953eversion 6694b8daffac5a8661071f085608afc78f7acd08≥ 5.10.37 and < 5.10.261≥ 5.11.21 and < 5.12≥ 5.12.4 and < 5.13version 5.13 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.8 | CVSS 3.1 | High | 2.0 | 6.0 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 8.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- CVSS changed · 8.8
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/ef4c38d30b3744e89eb5048218904bb629ea8d47
- git.kernel.org/stable/c/42d758a09d2c46c42357ecde9a5492f015bde2e5
- git.kernel.org/stable/c/9e0a3f642e607848669235f5069f35640abbfc88
- git.kernel.org/stable/c/daedde7f024ecf88bc8e832ed40cf2c795f0796a
- git.kernel.org/stable/c/0f2a35a0c7ea7da347b814750eaa78adf3582381
- git.kernel.org/stable/c/52adb2dff7ce3d8430e2bdc5988b618a430def85
- git.kernel.org/stable/c/8d65decde9afd2bd78bcfffdc0df73b82a0b5509
- git.kernel.org/stable/c/278a5659c391fe5afe5f9ce1bad1fd24e90144f1
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 11h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 11h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-64475 is "vfio/pci: Release the VGA arbiter client on register_device() failure", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.8 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.