block: fix blktrace debugfs entries leakage
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
block: fix blktrace debugfs entries leakage
Commit 99d055b4fd4b ("block: remove per-disk debugfs files in blk_unregister_queue") moves blk_trace_shutdown() from blk_release_queue() to blk_unregister_queue(), this is safe if blktrace is created through sysfs, however, there is a regression in corner case.
blktrace can still be enabled after del_gendisk() through ioctl if the disk is opened before del_gendisk(), and if blktrace is not shutdown through ioctl before closing the disk, debugfs entries will be leaked.
Fix this problem by shutdown blktrace in disk_release(), this is safe because blk_trace_remove() is reentrant.
From the CVE record · Linux
The Linux kernel can leak blktrace debugfs entries when a disk is opened before del_gendisk(), blktrace is enabled through ioctl afterward, and blktrace is not shut down through ioctl before the disk is closed. The supplied information does not specify authentication requirements or whether an attacker must interact with the disk.
Engineers running Linux kernels with blktrace should check their versions; affected versions were not specified.