s390/cio: use generic driver_override infrastructure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
s390/cio: use generic driver_override infrastructure
When a driver is probed through __driver_attach(), the bus' match() callback is called without the device lock held, thus accessing the driver_override field without a lock, which can cause a UAF.
Fix this by using the driver-core driver_override infrastructure taking care of proper locking internally.
Note that calling match() from __driver_attach() without the device lock held is intentional. [1]
From the CVE record · Linux
The Linux kernel's s390/cio driver matching code can access the driver_override field without a lock when a driver is probed through __driver_attach(), causing a use-after-free. The input does not establish what an attacker can do with this condition or whether network access, authentication, or user interaction is required.
Teams running the Linux kernel should check whether their kernel includes the affected s390/cio code; affected versions were not provided.