CVE-2026-64476

CVE CVE-2026-64476EUVD EUVD-2026-48820Veröffentlicht 2026-07-25T08:51:38.000Z

Was das Advisory beschreibt

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.

Quelle: EUVD (ENISA), im Wortlaut der Meldung.

Produkte, die das Advisory nennt

Diese Angaben stammen aus der Meldung selbst, nicht aus einer Prüfung durch uns.

• Linux — Linux 7ab5e10eda02da1d9562ffde562c51055d368e9c <4575e9aac5336d1365138c0284773bf8da4b1fa3; patch: 6.18.39; patch: 7.2-rc2; 7ab5e10eda02da1d9562ffde562c51055d368e9c <654710ef3135c4546b20a903bc23a51b0c44d6c8; patch: 7.1.4; 7ab5e10eda02da1d9562ffde562c51055d368e9c <332d785f9ae426eeeb92527872adf09d84101ba3; patch: 6.12.96; patch: 0; 7ab5e10eda02da1d9562ffde562c51055d368e9c <b98296816d31441b307ef9fa8670dcf5a55e5505; 7ab5e10eda02da1d9562ffde562c51055d368e9c <f6c67cf0051f96ba61d186731d3d9409b9927db2; 5.19; patch: 6.6.145; patch: 6.1.178; 7ab5e10eda02da1d9562ffde562c51055d368e9c <062b820290bcb9778e43a73597df76e9bb08acfb

Die genannten Versionen sind die Angabe der Meldung. Patchlage vergleicht keine Versionsnummern und leitet aus ihnen keine Aussage ab — welche Version installiert ist, muss ein Mensch nachsehen.

Im Produktkatalog geführt

Für diese Produkte kann ein Bestand in Patchlage erfasst werden. Ein Advisory dazu erscheint am Morgen danach im Lagebericht.

• Linux — Linux

Patchlage meldet Treffer und Verdachtsfälle. Zu allem anderen sagt dieses System nichts — weder diese Seite noch der Lagebericht behauptet je, dass ein Bestand sicher ist.