nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 872d26a391da92ed8f0c0f5cb5fef428067b7f30 · < 70154e8d015c9b4fb56c1a2ef1fc8b83d45c7f68| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length
If the host sends an H2CData command with an invalid DATAL, the kernel may crash in nvmet_tcp_build_pdu_iovec().
Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 lr : nvmet_tcp_io_work+0x6ac/0x718 [nvmet_tcp] Call trace: process_one_work+0x174/0x3c8 worker_thread+0x2d0/0x3e8 kthread+0x104/0x110
Fix the bug by raising a fatal error if DATAL isn't coherent with the packet size. Also, the PDU length should never exceed the MAXH2CDATA parameter which has been communicated to the host in nvmet_tcp_handle_icreq().
From the CVE record · Linux
The Linux kernel’s nvmet-tcp component can dereference a null pointer when a host sends an H2CData command with an invalid DATAL length. A host communicating with the target can trigger a kernel crash; the input does not specify whether authentication is required.
Operators running the Linux kernel with nvmet-tcp should check their installations; affected versions are not specified.