nvme-tcp: reject a read that transferred too few bytes
Summary
| CVE | CVE-2026-89480 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-11 20:19:29 UTC |
| Updated | 2026-09-11 20:19:29 UTC |
| Description | 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. |
Risk And Classification
EPSS: 0.001680000 probability, percentile 0.063280000 (date 2026-09-12)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 3f2304f8c6d6ed97849057bd16fee99e434ca796 99066cf9bba175f610ceb61a35f6fc9fbc33ff65 git | Not specified |
| CNA | Linux | Linux | affected 3f2304f8c6d6ed97849057bd16fee99e434ca796 8a02ad98798fd01f51f648c1fdd8f3c9d07195d3 git | Not specified |
| CNA | Linux | Linux | affected 3f2304f8c6d6ed97849057bd16fee99e434ca796 832a685efeb5d925ee7d30011d2dbe45f81447a3 git | Not specified |
| CNA | Linux | Linux | affected 3f2304f8c6d6ed97849057bd16fee99e434ca796 7fa3f73f6c8ddc5f0425b50fb2a626a782ef7d12 git | Not specified |
| CNA | Linux | Linux | affected 5.0 | Not specified |
| CNA | Linux | Linux | unaffected 5.0 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.109 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.50 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.4 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3-rc1 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/99066cf9bba175f610ceb61a35f6fc9fbc33ff65 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/8a02ad98798fd01f51f648c1fdd8f3c9d07195d3 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/7fa3f73f6c8ddc5f0425b50fb2a626a782ef7d12 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/832a685efeb5d925ee7d30011d2dbe45f81447a3 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.