PCI: Allow per function PCI slots to fix slot reset on s390
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.112, 6.18.52, 7.2.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: PCI: Allow per function PCI slots to fix slot reset on s390 On s390 systems, which use a machine level hypervisor, PCI devices are always accessed through a form of PCI pass-through which fundamentally operates on a per PCI function granularity. This is also reflected in the s390 PCI hotplug driver which creates hotplug slots for individual PCI functions. Its reset_slot() function, which is a wrapper for zpci_hot_reset_device(), thus also resets individual functions. Currently, the pci_create_slot() assigns the same pci_slot object to multifunction devices. This approach worked fine on s390 systems that only exposed virtual functions as individual PCI domains to the operating system. Since commit 44510d6fa0c0 ("s390/pci: Handling multifunctions") s390 supports exposing the topology of multifunction PCI devices by grouping them in a shared PCI domain. This creates a problem when resetting a function through the hotplug driver's slot_reset() interface. When attempting to reset a function through the hotplug driver, the shared slot assignment causes the wrong function to be reset instead of the intended one. It also leaks memory as we do create a pci_slot object for the function, but don't correctly free it in pci_slot_release(). Add a flag for struct pci_slot to allow per function PCI slots for functions managed through a hypervisor, which exposes individual PCI functions while retaining the topology. Since we can use all 8 bits for slot 'number' (for ARI devices), change slot 'number' u16 to account for special values PCI_SLOT_PLACEHOLDER and PCI_SLOT_ALL_DEVICES.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 44510d6fa0c00aa90b80075caa6b313b25927475 · fixed in b4a80e9e639cf09ef5c66b7f262c9cb5ab37bdde; From 44510d6fa0c00aa90b80075caa6b313b25927475 · fixed in 0d1a7d67f45645106578d65181e4e492dd20ed79; From 44510d6fa0c00aa90b80075caa6b313b25927475 · fixed in 2050d900f9adbd6d6f38d30e182bcd9ad3108467; From 44510d6fa0c00aa90b80075caa6b313b25927475 · fixed in ecdcceed4d377b02d4ea036b65f83f962c38ede7; From 44510d6fa0c00aa90b80075caa6b313b25927475 · fixed in dcc5bec09e23bbc4f9de055a11fce9937244f2c8
- Linux Linux
5.8
- KernelLinux
From 5.8.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.5