CVE-2026-80789nvmet-tcp: bound SGL data length before allocating command buffers
- —Not scoredno CVSS score yet
- 0.23%Exploitation in 30 daysEPSS · top 86% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: bound SGL data length before allocating command buffers nvmet_tcp_map_data() reads the host-controlled 32-bit sgl->length and, for the in-capsule offset descriptor (type 0x01), checks it against port->inline_data_size before use. Any other SGL descriptor type -- including the non-inline transport SGL data-block descriptor (type (NVME_TRANSPORT_SGL_DATA_DESC << 4) | NVME_SGL_FMT_TRANSPORT_A, the type a real host uses for out-of-capsule writes) skips that check entirely and falls straight through to: cmd->req.sg = sgl_alloc(len, GFP_KERNEL, &cmd->req.sg_cnt); with len taken directly from the wire, unbounded up to 4 GiB. nvmet_req_init() only parses the command and never inspects sgl->length, and nvmet_check_transfer_len() -- the only other place transfer_len is validated -- runs later, from req->execute(), after the allocation has already happened. For a write command the target responds with an R2T and parks the command waiting for the host to send the data; if the host (or an unauthenticated peer that simply never follows up) never does, the sgl_alloc() buffer stays resident for the life of the command. NVMe/TCP has no mandatory authentication in the default configuration, so any peer able to reach the target portal and complete a Fabrics connect can drive this with a single crafted command, repeatable across queues and connections for amplification. This is unbounded kernel memory allocation triggered by a remote, effectively unauthenticated peer. Validate len against the same NVMET_TCP_MAXH2CDATA ceiling this file already uses to bound per-PDU H2C data, for every SGL descriptor type, before doing any allocation. This closes the gap for the non-inline descriptor while leaving the existing, tighter inline_data_size check in place for the in-capsule case. Runtime-verified on a v6.19 KASAN stand: with this bound in place, a crafted write command carrying an oversized non-inline SGL length is rejected before sgl_alloc() runs, where the same request previously drove an unbounded ~256 MiB kernel allocation (up to 4 GiB) that stayed resident pending an R2T the host never satisfies.
Timeline
ID reserved
By Linux
- 9 days later
· 9 days later
Published
- 45 days later
· 45 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.23% · top 86% of all CVEs (18 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < f6e51b09cbaa5f6f6e6a3a9dafa666f76c37aab5
- affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < f63e89a0310264264923f84406dea05fe752de62
- affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < 0952541b153e258b99d39cdb03ea6919fdeb41d0
- affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < 25ad03d5c0e858c4b63f1e4b6d461d2af1b30b22
- affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < d2acc96c528d589f5827cfb90e8e9229dd9d8cb4
- affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < 6d27199ebe8cb223022150f74be13f154a964474
- affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < 14dbe37681a6a7e346fc147bb363ec7cca3180a0
- affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < d895e66628f939edbb98608f6e033d3d39e6e546
- affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < 4a3f00262a044e8e15064b1a6860968bf0500bf4
- affected 5.0
- unaffected < 5.0
- unaffected 5.10.269 – ≤ 5.10.*
- unaffected 5.15.220 – ≤ 5.15.*
- unaffected 6.1.187 – ≤ 6.1.*
- unaffected 6.6.156 – ≤ 6.6.*
- unaffected 6.12.106 – ≤ 6.12.*
- unaffected 6.18.47 – ≤ 6.18.*
- unaffected 7.1.11 – ≤ 7.1.*
- unaffected 7.2.1 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References9
- https://git.kernel.org/stable/c/f6e51b09cbaa5f6f6e6a3a9dafa666f76c37aab5 (opens in a new tab)
- https://git.kernel.org/stable/c/f63e89a0310264264923f84406dea05fe752de62 (opens in a new tab)
- https://git.kernel.org/stable/c/0952541b153e258b99d39cdb03ea6919fdeb41d0 (opens in a new tab)
- https://git.kernel.org/stable/c/25ad03d5c0e858c4b63f1e4b6d461d2af1b30b22 (opens in a new tab)
- https://git.kernel.org/stable/c/d2acc96c528d589f5827cfb90e8e9229dd9d8cb4 (opens in a new tab)
- https://git.kernel.org/stable/c/6d27199ebe8cb223022150f74be13f154a964474 (opens in a new tab)
- https://git.kernel.org/stable/c/14dbe37681a6a7e346fc147bb363ec7cca3180a0 (opens in a new tab)
- https://git.kernel.org/stable/c/d895e66628f939edbb98608f6e033d3d39e6e546 (opens in a new tab)
- https://git.kernel.org/stable/c/4a3f00262a044e8e15064b1a6860968bf0500bf4 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-71432 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-80789)Record last updated .