Linux kernel invalid device cleanup in NVMe target P2P allocation
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ bcd9a0797d73eeff659582f23277e7ab6e5f18f3 · < ce79a6c5cc1b8054ec8d3eba16adda4a36113438| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nvmet: use the local P2P device on metadata allocation failure
nvmet_req_alloc_p2pmem_sgls() assigns req->p2p_dev only after the data and metadata SGL allocations succeed. If the data allocation succeeds but the metadata allocation fails, out_free_sg passes req->p2p_dev to pci_p2pmem_free_sgl() before that assignment has taken place.
Pass the local p2p_dev argument instead, so cleanup uses the same PCI device as the successful data allocation.
From the CVE record · Linux
The Linux kernel's nvmet code can pass an unassigned P2P device to memory cleanup when a data allocation succeeds but a metadata allocation fails. The input does not specify what an attacker could do or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with nvmet should check their versions; affected versions are not specified.