ublk: validate auto buf reg before taking uring_cmd
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 |
|
|
6.18.577.2.67.3In the Linux kernel, the following vulnerability has been resolved:
ublk: validate auto buf reg before taking uring_cmd
With UBLK_F_AUTO_BUF_REG, invalid sqe->addr can fail after ublk_fill_io_cmd() has set UBLK_IO_FLAG_ACTIVE. The uring_cmd is completed while the tag stays active, which can hang teardown.
Split validation from buffer apply so the check has no side effects, then take the uring_cmd and store the already-validated buffer. Apply the same order in FETCH so io->buf is not written before __ublk_fetch() state checks.
From the CVE record · Linux
The Linux kernel’s ublk component can leave an I/O tag active when UBLK_F_AUTO_BUF_REG is enabled and an invalid buffer address is supplied. This can hang teardown. The input does not specify whether exploitation requires local access, authentication, or user interaction.
Engineers running Linux kernels with the ublk component should check their versions; affected versions are not specified.