cveboard RSS feed

CVE-2026-89795

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2026
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

PCI: Allow per function PCI slots to fix slot reset on s390

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.

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
unaffected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
44510d6fa0c00aa90b80075caa6b313b25927475affectedgitb4a80e9e639cf09ef5c66b7f262c9cb5ab37bddeUnavailableNone listed
44510d6fa0c00aa90b80075caa6b313b25927475affectedgit0d1a7d67f45645106578d65181e4e492dd20ed79UnavailableNone listed
44510d6fa0c00aa90b80075caa6b313b25927475affectedgit2050d900f9adbd6d6f38d30e182bcd9ad3108467UnavailableNone listed
44510d6fa0c00aa90b80075caa6b313b25927475affectedgitecdcceed4d377b02d4ea036b65f83f962c38ede7UnavailableNone listed
44510d6fa0c00aa90b80075caa6b313b25927475affectedgitdcc5bec09e23bbc4f9de055a11fce9937244f2c8UnavailableNone listed

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
affected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
5.8affectedUnavailableUnavailableUnavailableNone listed
0unaffectedsemver5.8UnavailableNone listed
6.6.160unaffectedsemverUnavailable6.6.*None listed
6.12.112unaffectedsemverUnavailable6.12.*None listed
6.18.52unaffectedsemverUnavailable6.18.*None listed
7.2.5unaffectedsemverUnavailable7.2.*None listed
7.3unaffectedoriginal_commit_for_fixUnavailable*None listed