nvme-tcp: reject a read that transferred too few bytes
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel fca3ebb63e5c82561cd9934365dcc0d068008006, Kernel 7fa3f73f6c8ddc5f0425b50fb2a626a782ef7d12, Kernel 832a685efeb5d925ee7d30011d2dbe45f81447a3 and 12 more.
In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: reject a read that transferred too few bytes nvme_tcp_recv_data() completes a request once the current C2HData PDU has been consumed. Nothing compares the total bytes received against the length the command asked for: struct nvme_tcp_request has no receive-side counter, queue->data_remaining is per queue, and blk_mq_end_request() completes for blk_rq_bytes(rq) unconditionally with no residual concept anywhere above. A controller can therefore answer a 4096-byte read with 512 bytes and have it reported as a complete read; user space then gets 4096 bytes of which 3584 are whatever was already in the page. I reproduced that with a test target. Count the bytes received and refuse to complete a successful read whose count does not match, at the two NVME_TCP_F_DATA_SUCCESS paths and in nvme_tcp_process_nvme_cqe(). The success test shifts req->status right by one, because the driver keeps the wire value there and shifts it on completion, so the check must see what the completion path will see. Only REQ_OP_READ is checked, because there the length comes from the sectors the request covers; a passthrough command is built by its submitter, which picks both command and buffer, so the kernel has nothing to compare against.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <fca3ebb63e5c82561cd9934365dcc0d068008006, >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <7fa3f73f6c8ddc5f0425b50fb2a626a782ef7d12, >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <832a685efeb5d925ee7d30011d2dbe45f81447a3, >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <8a02ad98798fd01f51f648c1fdd8f3c9d07195d3, >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <99066cf9bba175f610ceb61a35f6fc9fbc33ff65, >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <a5c1bb0fb1bab2f24a081339c145870697f6d220, >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <aa107e3a68f4af177d60f2d87679e7f67179a36c, >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <b674af31d044a86bd094ba8bb8f2bb92fb49aac5, =5.0 | fca3ebb63e5c82561cd9934365dcc0d068008006, 7fa3f73f6c8ddc5f0425b50fb2a626a782ef7d12, 832a685efeb5d925ee7d30011d2dbe45f81447a3, 8a02ad98798fd01f51f648c1fdd8f3c9d07195d3, 99066cf9bba175f610ceb61a35f6fc9fbc33ff65, a5c1bb0fb1bab2f24a081339c145870697f6d220, aa107e3a68f4af177d60f2d87679e7f67179a36c, b674af31d044a86bd094ba8bb8f2bb92fb49aac5 |
| linux-kernel: Kernel | >=5.11.0 <5.15.221, >=5.16.0 <6.1.188, >=6.13.0 <6.18.50, >=6.19.0 <7.2.4, >=6.2.0 <6.6.157, >=6.7.0 <6.12.109, >=5.0.0 <5.10.273 | 5.15.221, 6.1.188, 6.18.50, 7.2.4, 6.6.157, 6.12.109, 5.10.273 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket