CVE Catalog

CVE-2026-80788

Low risk· EPSS 9%
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.20%

9th percentile - higher than 9% of all known CVEs

Summary

In the Linux kernel's nvmet-tcp subsystem, a vulnerability allows a remote initiator to control the size of SGL allocations, triggering a kernel warning (WARN_ON_ONCE_GFP) for very large allocations. The issue is fixed by adding GFP_NOWARN to the allocation flags to avoid kernel panic on systems with panic-on-warn enabled.

Risk Assessment

A remote attacker can cause a kernel warning, which on systems with panic-on-warn enabled leads to a system crash (DoS).

Recommendation

Apply the Linux kernel update containing the fix for CVE-2026-80788. If not possible, consider disabling panic-on-warn or restricting access to nvmet-tcp services.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS