ublk: make sure ubq->canceling is set when queue is frozen
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:
ublk: make sure ubq->canceling is set when queue is frozen
Now ublk driver depends on `ubq->canceling` for deciding if the request can be dispatched via uring_cmd & io_uring_cmd_complete_in_task().
Once ubq->canceling is set, the uring_cmd can be done via ublk_cancel_cmd() and io_uring_cmd_done().
So set ubq->canceling when queue is frozen, this way makes sure that the flag can be observed from ublk_queue_rq() reliably, and avoids use-after-free on uring_cmd.
From the CVE record · Linux
The Linux kernel ublk driver can encounter a use-after-free involving uring_cmd when a queue is frozen and its canceling flag is not set reliably. The input does not specify how an attacker could trigger this condition, or whether access or user interaction is required.
Engineers running Linux kernels with the ublk driver should check whether their kernel is affected; affected versions are not specified.