PoC Monitor
← All CVEs
CVE-2026-89480published 11 Sep 2026 19:43 UTCData: JSON · API

Linux

nvme-tcp: reject a read that transferred too few bytes

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.5high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= 3f2304f8c6d6ed97849057bd16fee99e434ca796, < b674af31d044a86bd094ba8bb8f2bb92fb49aac5
  • >= 3f2304f8c6d6ed97849057bd16fee99e434ca796, < a5c1bb0fb1bab2f24a081339c145870697f6d220
  • >= 3f2304f8c6d6ed97849057bd16fee99e434ca796, < aa107e3a68f4af177d60f2d87679e7f67179a36c
  • >= 3f2304f8c6d6ed97849057bd16fee99e434ca796, < fca3ebb63e5c82561cd9934365dcc0d068008006
  • >= 3f2304f8c6d6ed97849057bd16fee99e434ca796, < 99066cf9bba175f610ceb61a35f6fc9fbc33ff65
  • >= 3f2304f8c6d6ed97849057bd16fee99e434ca796, < 8a02ad98798fd01f51f648c1fdd8f3c9d07195d3
  • >= 3f2304f8c6d6ed97849057bd16fee99e434ca796, < 832a685efeb5d925ee7d30011d2dbe45f81447a3
  • >= 3f2304f8c6d6ed97849057bd16fee99e434ca796, < 7fa3f73f6c8ddc5f0425b50fb2a626a782ef7d12

Fixed in b674af31d044a86bd094ba8bb8f2bb92fb49aac5, a5c1bb0fb1bab2f24a081339c145870697f6d220, aa107e3a68f4af177d60f2d87679e7f67179a36c, fca3ebb63e5c82561cd9934365dcc0d068008006, 99066cf9bba175f610ceb61a35f6fc9fbc33ff65, 8a02ad98798fd01f51f648c1fdd8f3c9d07195d3, 832a685efeb5d925ee7d30011d2dbe45f81447a3, 7fa3f73f6c8ddc5f0425b50fb2a626a782ef7d12

Linux Linux
  • 5.0

Fixed in 0, 5.10.273, 5.15.221, 6.1.188, 6.6.157, 6.12.109, 6.18.50, 7.2.4, 7.3

Mitigation

Upgrade Linux to b674af31d044a86bd094ba8bb8f2bb92fb49aac5 or a5c1bb0fb1bab2f24a081339c145870697f6d220 or aa107e3a68f4af177d60f2d87679e7f67179a36c or fca3ebb63e5c82561cd9934365dcc0d068008006 or 99066cf9bba175f610ceb61a35f6fc9fbc33ff65 or 8a02ad98798fd01f51f648c1fdd8f3c9d07195d3 or 832a685efeb5d925ee7d30011d2dbe45f81447a3 or 7fa3f73f6c8ddc5f0425b50fb2a626a782ef7d12 or later.

Upgrade Linux to 0 or 5.10.273 or 5.15.221 or 6.1.188 or 6.6.157 or 6.12.109 or 6.18.50 or 7.2.4 or 7.3 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published11 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.