Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-64476: vfio/pci: Latch disable_idle_d3 per device

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
  • Fixed version: Linux Linux 062b820290bcb9778e43a73597df76e9bb08acfb, 332d785f9ae426eeeb92527872adf09d84101ba3, 4575e9aac5336d1365138c0284773bf8da4b1fa3.

Low priority for now. Upgrade to Linux Linux 062b820290bcb9778e43a73597df76e9bb08acfb, 332d785f9ae426eeeb92527872adf09d84101ba3, 4575e9aac5336d1365138c0284773bf8da4b1fa3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Latch disable_idle_d3 per device When disable_idle_d3 was introduced in vfio-pci, it directly manipulated the device power state with pci_set_power_state(). There were no refcounts to maintain or balanced operations, we could unconditionally bring the device to D0 and conditionally move it to D3hot. Therefore the module parameter was made writable. Later, in commit c61302aa48f7 ("vfio/pci: Move module parameters to vfio_pci.c"), as part of the vfio-pci-core split, the writable aspect of the module parameter was nullified. The parameter value could still be changed through sysfs, but the vfio-pci driver latched the values into vfio-pci-core globals at module init. Loading the vfio-pci module, or unloading and reloading, with non-default or different values could change the globals relative to existing devices bound to vfio-pci variant drivers. Runtime PM was introduced in commit 7ab5e10eda02 ("vfio/pci: Move the unused device into low power state with runtime PM"), which marks the point where power states became refcounted. PM get and put operations need to be balanced, but the same module operations noted above can change the global variables relative to those devices already bound to vfio-pci variant drivers. This introduces a window where PM operations can now become unbalanced. To resolve this with a narrow footprint for stable backports, the disable_idle_d3 flag is latched into the vfio_pci_core_device at the time of initialization, such that the device always operates with a consistent value. NB. vfio_pci_dev_set_try_reset() now unconditionally raises the runtime PM usage count around bus reset to account for disable_idle_d3 becoming a per-device rather than global flag. When this flag is set, the additional get/put pair is harmless and allows continued use of the shared vfio_pci_dev_set_pm_runtime_get() helper.

—No exploit Fix available
Published
Jul 25, 2026
Updated
Aug 17, 2026
EPSS
0.1% · 7th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-64476

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.19affected
    • 7ab5e10eda02da1d9562ffde562c51055d368e9c and later · before 332d785f9ae426eeeb92527872adf09d84101ba3affected · git
    • 7ab5e10eda02da1d9562ffde562c51055d368e9c and later · before 654710ef3135c4546b20a903bc23a51b0c44d6c8affected · git
    • 7ab5e10eda02da1d9562ffde562c51055d368e9c and later · before b98296816d31441b307ef9fa8670dcf5a55e5505affected · git
    • 7ab5e10eda02da1d9562ffde562c51055d368e9c and later · before f6c67cf0051f96ba61d186731d3d9409b9927db2affected · git
    • 7ab5e10eda02da1d9562ffde562c51055d368e9c and later · before 062b820290bcb9778e43a73597df76e9bb08acfbaffected · git
    • 7ab5e10eda02da1d9562ffde562c51055d368e9c and later · before 4575e9aac5336d1365138c0284773bf8da4b1fa3affected · git
    • before 5.19not affected · semver
    • 6.1.178 and later · up to and including 6.1.*not affected · semver
    • 6.6.145 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:12linux-6.12before 6.12.100-1~deb12u16.12.100-1~deb12u1
Debian:13linuxbefore 6.12.96-16.12.96-1
Debian:14linuxbefore 7.1.4-17.1.4-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-64473Jul 25, 2026 · vfio: Remove device debugfs before releasing devres
    0Monitor
  • ← EarlierCVE-2026-64474Jul 25, 2026 · vfio: prevent infinite loop in vfio_mig_get_next_state() on blocked arc
    0Monitor
  • Later →CVE-2026-64477Jul 25, 2026 · x86,fs/resctrl: Prevent out-of-bounds access while offlining CPU when SNC enabled
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux062b820290bcb9778e43a73597df76e9bb08acfbVendor (CNA)
Linux Linux332d785f9ae426eeeb92527872adf09d84101ba3Vendor (CNA)
Linux Linux4575e9aac5336d1365138c0284773bf8da4b1fa3Vendor (CNA)
Linux Linux654710ef3135c4546b20a903bc23a51b0c44d6c8Vendor (CNA)
Linux Linuxb98296816d31441b307ef9fa8670dcf5a55e5505Vendor (CNA)
Linux Linuxf6c67cf0051f96ba61d186731d3d9409b9927db2Vendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.100-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records