Answer in brief
CVE-2026-52994 records a Medium severity (CVSS 5.5) vulnerability in vsock/virtio: fix MSG_ZEROCOPY pinned-pages accounting. 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 5.5. 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 | 6.7 | Not reported |
| Linux/Linuxgeneric | >=581512a6dc939ef122e49336626ae159f3b8a345 <6af1736b5810bc8a4a43a8518530113f5a757dc1 || >=581512a6dc939ef122e49336626ae159f3b8a345 <d0117950075f0a9d5944980784c719d8ebcd4bff || >=581512a6dc939ef122e49336626ae159f3b8a345 <1cb36e252211506f51095fe7ced8286cc77b4c80 | 6af1736b5810bc8a4a43a8518530113f5a757dc1, d0117950075f0a9d5944980784c719d8ebcd4bff, 1cb36e252211506f51095fe7ced8286cc77b4c80 |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: fix MSG_ZEROCOPY pinned-pages accounting virtio_transport_init_zcopy_skb() uses iter->count as the size argument for msg_zerocopy_realloc(), which in turn passes it to mm_account_pinned_pages() for RLIMIT_MEMLOCK accounting. However, this function is called after virtio_transport_fill_skb() has already consumed the iterator via __zerocopy_sg_from_iter(), so on the last skb, iter->count will be 0, skipping the RLIMIT_MEMLOCK enforcement. Pass pkt_len (the total bytes being sent) as an explicit parameter to virtio_transport_init_zcopy_skb() instead of reading the already-consumed iter->count. This matches TCP and UDP, which both call msg_zerocopy_realloc() with the original message size.
Quoted source text, attributed separately from HOL analysis.