nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 872d26a391da92ed8f0c0f5cb5fef428067b7f30 · < ab200d71553bdcf4de554a5985b05b2dd606bc57| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec
nvmet_tcp_build_pdu_iovec() could walk past cmd->req.sg when a PDU length or offset exceeds sg_cnt and then use bogus sg->length/offset values, leading to _copy_to_iter() GPF/KASAN. Guard sg_idx, remaining entries, and sg->length/offset before building the bvec.
From the CVE record · Linux
The Linux kernel’s nvmet-tcp code can read past a scatter-gather list when a PDU length or offset exceeds its entry count. A network attacker who can send such a PDU to an nvmet-tcp target could trigger a kernel fault; the input does not specify whether authentication is required.
Engineers running Linux kernels with nvmet-tcp should check whether their kernel includes the bounds-check fix; affected versions are not specified.