Answer in brief
CVE-2026-90051 records a High severity (CVSS 7.8) vulnerability in tcp: reject non zerocopy devmem tx. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=bd61848900bff597764238f3a8ec67c815cd316e <2151b2bcf6fcec52665f606eed20da068447f0b7 || >=bd61848900bff597764238f3a8ec67c815cd316e <b04326c7927af7048fd4e730f5770cca350d0a60 || >=bd61848900bff597764238f3a8ec67c815cd316e <125755776bc6d4dd53eaf551c87e3d460625d638 | 2151b2bcf6fcec52665f606eed20da068447f0b7, b04326c7927af7048fd4e730f5770cca350d0a60, 125755776bc6d4dd53eaf551c87e3d460625d638 |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
In the Linux kernel, the following vulnerability has been resolved: tcp: reject non zerocopy devmem tx Devmem tcp tx doesn't work without zero-copy, however it's not currently enforced if NETIF_F_SG isn't present. In this case, tcp_sendmsg_locked() will try the copy path and try to copy data from an iovec which consists of offsets into the dma-buf and would normally fail. Moreover, d9c56501c72fd ("net: tcp: block mixing readable and unreadable frags") relies on that and assumes that the devmem binding is present IFF we're using the zero-copy path, which can be used to mix net-iov and pages in a single skb, and break invariants. Let's reject devmem tx without zero-copy. Note, the parameter check the patch is modifying is too loose, we can create an io_uring request with dmabuf_id and all ZC flags, but which won't have the binding. We replace it with stricter validation.
Quoted source text, attributed separately from HOL analysis.