nvmet-auth: Synchronize timeout work during SQ teardown
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1a70200f404ae210b4f0334e3936e84f8edb6bc8 · < eaa948c0e19b1bb2d93262207bca0c3d19cc3406| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nvmet-auth: Synchronize timeout work during SQ teardown
nvmet_auth_sq_free() cancels auth_expired_work with cancel_delayed_work(). If the work has already started, cancellation does not wait for the callback. Transport teardown can consequently free or reuse the queue containing struct nvmet_sq while nvmet_auth_expired_work() still accesses that SQ.
Add a teardown-specific helper that synchronously drains the delayed work before freeing authentication state, and use it from nvmet_sq_destroy(). Keep the non-synchronous helper for in-band authentication state cleanup, where the SQ owner remains alive.
From the CVE record · Linux
The Linux kernel’s nvmet-auth code can free or reuse a submission queue while a timeout callback is still accessing it. This can cause a use-after-free during transport teardown if the callback has already started. The input does not establish how an attacker could trigger this or whether authentication or user interaction is required.
Engineers running Linux kernels with nvmet-auth should check their kernel’s status; affected versions are not specified.