s390/pci: Fix duplicate pci_dev_put() in disable_slot() when PF has child VFs
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.12.296.14.76.15In the Linux kernel, the following vulnerability has been resolved:
s390/pci: Fix duplicate pci_dev_put() in disable_slot() when PF has child VFs
With commit bcb5d6c76903 ("s390/pci: introduce lock to synchronize state of zpci_dev's") the code to ignore power off of a PF that has child VFs was changed from a direct return to a goto to the unlock and pci_dev_put() section. The change however left the existing pci_dev_put() untouched resulting in a doubple put. This can subsequently cause a use after free if the struct pci_dev is released in an unexpected state. Fix this by removing the extra pci_dev_put().
From the CVE record · Linux
The Linux kernel’s s390/pci disable_slot() path can release a PCI device reference twice when a physical function (PF) with child virtual functions (VFs) is powered off, potentially causing a use-after-free. The input does not specify how an attacker could trigger this condition, whether authentication is needed, or whether user interaction is required.
Engineers running the Linux kernel on s390 systems using PCI physical functions with child virtual functions should check their installations; affected versions are not specified.