CVE-2026-89480
CVE CVE-2026-89480EUVD EUVD-2026-76386Published 2026-09-11T19:43:35.000ZLast changed 2026-09-14T12:00:17.000ZCVSS 7.5
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 6.6.157; patch: 7.2.4; patch: 6.1.188; 3f2304f8c6d6ed97849057bd16fee99e434ca796 <aa107e3a68f4af177d60f2d87679e7f67179a36c; 3f2304f8c6d6ed97849057bd16fee99e434ca796 <99066cf9bba175f610ceb61a35f6fc9fbc33ff65; patch: 0; 3f2304f8c6d6ed97849057bd16fee99e434ca796 <8a02ad98798fd01f51f648c1fdd8f3c9d07195d3; 3f2304f8c6d6ed97849057bd16fee99e434ca796 <7fa3f73f6c8ddc5f0425b50fb2a626a782ef7d12; patch: 6.18.50; 3f2304f8c6d6ed97849057bd16fee99e434ca796 <a5c1bb0fb1bab2f24a081339c145870697f6d220; 3f2304f8c6d6ed97849057bd16fee99e434ca796 <fca3ebb63e5c82561cd9934365dcc0d068008006; patch: 7.3-rc1; patch: 6.12.109; 5.0; patch: 5.15.221; 3f2304f8c6d6ed97849057bd16fee99e434ca796 <832a685efeb5d925ee7d30011d2dbe45f81447a3
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.