CVE-2026-80788

nvmet-tcp: Do not WARN on remotely-controlled oversized SGL allocations

N/A
Published: September 4, 2026 at 03:12 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.0872d26a391da92ed8f0c0f5cb5fef428067b7f30
Vendor states this is fixed in 737a3b535247226f6e1a7988fd9d6e63e7d6fc71 (fixed)
Vendor states this is fixed in 7b6a54d4e7b0da423c2b53ed293fd36b16c0b19e (fixed)
Vendor states this is fixed in 7fd6da0f28932442b51658bac4ff55565ca9b377 (fixed)
Vendor states this is fixed in 86cc450022473c4a29b43a09f3ec22a9ef566dac (fixed)
Vendor states this is fixed in 8d01f0d0e96485e39ad89b859ef85e1dc3020465 (fixed)
Vendor states this is fixed in 9b770e40bc00381e5ebf53653de5776773415be3 (fixed)
Vendor states this is fixed in 9c95f7e66c62ee6c6abedcf1c04311f430ff5833 (fixed)
Vendor states this is fixed in c509f20be1cabda3087810bb2d658d66b3f31f35 (fixed)
Vendor states this is fixed in e7077e6c45423dd2bb7de7b5fc4b018a8e6c4741 (fixed)
Vendor states this is fixed in 5.0 (unaffected)
Vendor states this is fixed in 5.10.267 (unaffected)
Vendor states this is fixed in 5.15.218 (unaffected)
Vendor states this is fixed in 6.1.185 (unaffected)
Vendor states this is fixed in 6.12.106 (unaffected)
Vendor states this is fixed in 6.18.47 (unaffected)
Vendor states this is fixed in 6.6.154 (unaffected)
Vendor states this is fixed in 7.1.11 (unaffected)
Vendor states this is fixed in 7.2.1 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card