s390/debug: Fix deadlock during unregister
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9372a82892c2caa6bccab9a4081166fa769699f8 · < 54e1259b75d6402a1d0cfb822b9bb2c507e53dab| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
s390/debug: Fix deadlock during unregister
Unregistering an s390dbf debug area while one of the associated debugfs files is being written to can cause a deadlock:
$ echo >.../vmur/level $ rmmod vmur =================================================== debugfs write debugfs_file_get() debug_unregister() mutex_lock(debug_mutex) debugfs_remove() wait for debugfs_file_put() debug_file_ops.write() debug_input() mutex_lock(debug_mutex) ==> DEADLOCK
Fix this by splitting debug_unregister() into an s390dbf and debugfs part, and running only the s390dbf part with debug_mutex locked.
From the CVE record · Linux
The Linux kernel's s390 debug facility can deadlock when a debug area is unregistered while an associated debugfs file is being written. This requires concurrent local operations; the input does not specify authentication requirements.
Engineers running Linux kernels that use s390 debug areas should check their versions; affected versions are not specified.