nvmet-tcp: fix page fragment cache leak in error path
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 872d26a391da92ed8f0c0f5cb5fef428067b7f30 · < 4dae393956093c807212918fd91a8fc70df15338| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nvmet-tcp: fix page fragment cache leak in error path
In nvmet_tcp_alloc_queue(), when a connection is closed during the allocation process (e.g., nvmet_tcp_set_queue_sock() returns -ENOTCONN), the error handling jumps to out_destroy_sq and then to out_ida_remove without draining the page fragment cache.
Although nvmet_tcp_free_cmd() is called in some error paths to release individual page fragments, the underlying page cache reference held by queue->pf_cache is never released. The first allocation using pf_cache is the call to nvmet_tcp_alloc_cmd() for queue->connect, which happens after ida_alloc() returns successfully. This results in a page leak each time a connection fails during allocation, which could lead to memory exhaustion over time if connections are repeatedly opened and closed.
Fix this by calling page_frag_cache_drain() before freeing the queue structure in the out_ida_remove label.
From the CVE record · Linux
The Linux kernel’s nvmet-tcp queue allocation error path can leak a page when a connection closes during allocation. Repeatedly opening and closing connections under this condition could exhaust memory over time; the input does not specify authentication requirements.
Engineers running Linux kernels with the nvmet-tcp target should check whether their kernel is affected; affected versions are not specified.