s390/pci: Fix missing device lock in zpci_report_status()
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.18.557.2.97.3In the Linux kernel, the following vulnerability has been resolved:
s390/pci: Fix missing device lock in zpci_report_status()
When pdev is non-NULL, zpci_report_status() accesses the device's driver. To get a consistent state matching the recovery, the device lock needs to be held. Do so by expanding the existing device lock critical section.
The lock only needs to be held when the pdev is non-NULL, so extract the pdev-specific reporting into a helper function which also adds a lockdep assertion to detect calls without the device lock held.
From the CVE record · Linux
The Linux kernel's s390 PCI status-reporting function can access a device's driver without holding the device lock, potentially reading a state inconsistent with recovery. The input does not describe an attacker action or specify access, authentication, or user-interaction conditions.
Teams running the Linux kernel on s390 systems with PCI devices should check their deployments; affected versions are not specified.