nvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready()
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.12.706.18.106.19In the Linux kernel, the following vulnerability has been resolved:
nvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready()
When the socket is closed while in TCP_LISTEN a callback is run to flush all outstanding packets, which in turns calls nvmet_tcp_listen_data_ready() with the sk_callback_lock held. So we need to check if we are in TCP_LISTEN before attempting to get the sk_callback_lock() to avoid a deadlock.
From the CVE record · Linux
The Linux kernel's nvmet-tcp listener can deadlock when a socket closes while in TCP_LISTEN and a callback tries to acquire a lock it already holds. The input does not specify whether an attacker can trigger this, or any network, authentication, or user-interaction requirements.
Engineers running the Linux kernel with nvmet-tcp should check their installations; affected versions are not specified.