CVE-2026-89969

CVE CVE-2026-89969EUVD EUVD-2026-80569Published 2026-09-16T10:32:49.000ZLast changed 2026-09-16T14:40:48.000ZCVSS 9.8

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: fix out-of-bounds write when receiving an over-long PDU nvmet_tcp_try_recv_pdu() reads a PDU header into the fixed 128-byte queue->pdu union, then computes the remaining payload length as queue->left = hdr->hlen - queue->offset + hdgst; and reads that many more bytes into &queue->pdu + queue->offset, without ever bounding the result against sizeof(queue->pdu). A struct nvme_tcp_icreq_pdu is itself 128 bytes, exactly the size of the union. Once a header digest has been negotiated (hdgst = 4), a second ICReq passes the hlen == nvmet_tcp_pdu_size() check but yields queue->left = 128 - 8 + 4 = 124, so bytes 8..132 are written into the 128-byte buffer -- 4 bytes past its end, over queue->hdr_digest and queue->data_digest. Those bytes are attacker-controlled (an ICReq carries no digest), and the duplicate ICReq is only rejected later, after the overflow. A remote unauthenticated host can thus corrupt kernel memory adjacent to the receive buffer. Reject any PDU whose declared length would read past the end of queue->pdu before the second recv.

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: 5.15.221; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 <a3f0bcfbaf3312a5754d1ce020a07d394669eb25; patch: 7.3-rc2; patch: 6.18.51; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 <3a385e0c39efbe34db8edd95900c123113ae3450; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 <14cc5a7e77731497d5bea70f3bb05df7eda982e4; patch: 0; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 <58dc6035b79c4c73c0cbf9ec9f68a7f117b2b3e6; patch: 5.10.270; patch: 6.12.110; patch: 6.6.157; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 <dbc4acbdb3ca8c81441368ad7409b8f77d4de8f6; patch: 7.2.5; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 <d95d342bc0ea82dc79e6362b2f1f997431750e4c; patch: 6.1.188; 5.0; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 <cf5f39d2b58f97e0cd1829c4a6aeef17f1607cca; 872d26a391da92ed8f0c0f5cb5fef428067b7f30 <4f84d42c53c49557fb1ef285c683b0a81b576c74

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

Patchlage 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.