s390/dasd: fix Oops in dasd_alias_get_start_dev due to missing pavgroup
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 8e09f21574ea3028d5629e5de759e0b196c690c5 · < d3a67c21b18f33c79382084af556557c442f12a6| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
s390/dasd: fix Oops in dasd_alias_get_start_dev due to missing pavgroup
Fix Oops in dasd_alias_get_start_dev() function caused by the pavgroup pointer being NULL.
The pavgroup pointer is checked on the entrance of the function but without the lcu->lock being held. Therefore there is a race window between dasd_alias_get_start_dev() and _lcu_update() which sets pavgroup to NULL with the lcu->lock held.
Fix by checking the pavgroup pointer with lcu->lock held.
From the CVE record · Linux
A race in the Linux kernel’s s390 DASD alias handling can cause a NULL-pointer dereference and kernel Oops. The input does not specify how an attacker could trigger it or whether network access, authentication, or user interaction is required.
Engineers running the Linux kernel with s390 DASD support should check their systems; affected versions are not specified.