nbd: Fix hung when signal interrupts nbd_start_device_ioctl()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5ea8d10802ec4c153a6e21eebaf412e2abd29736 · < 62006a72b05e0d38727eef5188700f2488be5e89| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nbd: Fix hung when signal interrupts nbd_start_device_ioctl()
syzbot reported hung task [1]. The following program is a simplified version of the reproducer:
int main(void) { int sv[2], fd;
if (socketpair(AF_UNIX, SOCK_STREAM, 0, sv) < 0) return 1; if ((fd = open("/dev/nbd0", 0)) < 0) return 1; if (ioctl(fd, NBD_SET_SIZE_BLOCKS, 0x81) < 0) return 1; if (ioctl(fd, NBD_SET_SOCK, sv[0]) < 0) return 1; if (ioctl(fd, NBD_DO_IT) < 0) return 1; return 0; }
When signal interrupt nbd_start_device_ioctl() waiting the condition atomic_read(&config->recv_threads) == 0, the task can hung because it waits the completion of the inflight IOs.
This patch fixes the issue by clearing queue, not just shutdown, when signal interrupt nbd_start_device_ioctl().
From the CVE record · Linux
The Linux kernel’s nbd code can leave a task hung if a signal interrupts nbd_start_device_ioctl() while it waits for receive threads to exit. A local user able to open and configure an nbd device can trigger the condition; the report does not specify whether additional privileges are required.
Engineers running Linux kernels with the nbd component should check their kernel versions against the vendor advisory; affected versions were not provided.