s390/dasd: protect device queue against concurrent access
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4fa52aa7a82f9226b3874a69816bda3af821f002 · < dc96fde8fcb2b896fd6c64802a7f4ece2e69b0be| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
s390/dasd: protect device queue against concurrent access
In dasd_profile_start() the amount of requests on the device queue are counted. The access to the device queue is unprotected against concurrent access. With a lot of parallel I/O, especially with alias devices enabled, the device queue can change while dasd_profile_start() is accessing the queue. In the worst case this leads to a kernel panic due to incorrect pointer accesses.
Fix this by taking the device lock before accessing the queue and counting the requests. Additionally the check for a valid profile data pointer can be done earlier to avoid unnecessary locking in a hot path.
From the CVE record · Linux
The Linux kernel’s s390/dasd profiling code accesses a device queue without protecting it from concurrent changes. Heavy parallel I/O, especially with alias devices enabled, can cause incorrect pointer accesses and a kernel panic. The input does not establish whether an attacker can trigger this remotely or needs authentication or user interaction.
Engineers running Linux kernels with s390/dasd devices should check their kernel versions; affected versions are not specified.