CVE Intelligence
Unknown

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

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.

Published Sep 4, 2026 · Updated Oct 19, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+1

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.2%
ahead of 9% of scored CVEs · Oct 27, 2026
Affects
Linux
Linux
CVSS base
—
Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Linux Linux ≥ 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and < 8d01f0d0e96485e39ad89b859ef85e1dc3020465≥ 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and < 7b6a54d4e7b0da423c2b53ed293fd36b16c0b19e≥ 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and < e7077e6c45423dd2bb7de7b5fc4b018a8e6c4741≥ 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and < 86cc450022473c4a29b43a09f3ec22a9ef566dac≥ 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and < c509f20be1cabda3087810bb2d658d66b3f31f35≥ 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and < 9c95f7e66c62ee6c6abedcf1c04311f430ff5833≥ 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and < 7fd6da0f28932442b51658bac4ff55565ca9b377≥ 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and < 9b770e40bc00381e5ebf53653de5776773415be3
and 2 more ≥ 872d26a391da92ed8f0c0f5cb5fef428067b7f30 and < 737a3b535247226f6e1a7988fd9d6e63e7d6fc71version 5.0
Vulnerable CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 15, 2026 → Oct 27, 2026 · 12 reading(s) · max 0.20%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Not enough vector or weakness data: use the affected application’s logs as a starting point.
application logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Record published
    Oct 15, 2026
  • Affected products added · linux/linux
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Received
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · NIST National Vulnerability Database
  • CVE published
    Sep 4, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 19, 2026 – Oct 19, 2026
  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

11 on the record

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

  • Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 16m
  • Unknown CVE-2026-99214 drm/vc4: hdmi: Move packet RAM enable to PM runtime 16m
  • Unknown CVE-2026-99213 vsock: treat TCP_CLOSING as once-established 16m
  • Unknown CVE-2026-99212 net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure 16m
  • Unknown CVE-2026-99211 netlink: reset skb headers before unicast and multicast filtering 16m
  • Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 16m

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CVSS score published by NVD, the CNA, CISA or GitHub so far.
  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No CWE classification.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-80788 is "nvmet-tcp: Do not WARN on remotely-controlled oversized SGL allocations", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.20% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.