Answer in brief
CVE-2026-46207 records a Unknown severity vulnerability in vsock/virtio: fix empty payload in tap skb for non-linear buffers. 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.
A CVSS score is not reported in the current record. 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 | >=4b0bf10eb077cb43c09746251ef3608d62c45667 <06747f52ab157591cec7e5623a759473b66ef6f6 || >=4b0bf10eb077cb43c09746251ef3608d62c45667 <52da6a74ca3de0fcda60301096b71534b3b18641 || >=4b0bf10eb077cb43c09746251ef3608d62c45667 <378b131a25bd1a5ee27ca199fe486c299d5350c5 || >=4b0bf10eb077cb43c09746251ef3608d62c45667 <3a3e3d90cbc79600544536723911657730759af3 | 06747f52ab157591cec7e5623a759473b66ef6f6, 52da6a74ca3de0fcda60301096b71534b3b18641, 378b131a25bd1a5ee27ca199fe486c299d5350c5, 3a3e3d90cbc79600544536723911657730759af3 |
| Linux/Linuxgeneric | 6.7 | Not reported |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 6, 2026
In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: fix empty payload in tap skb for non-linear buffers For non-linear skbs, virtio_transport_build_skb() goes through virtio_transport_copy_nonlinear_skb() to copy the original payload in the new skb to be delivered to the vsockmon tap device. This manually initializes an iov_iter but does not set iov_iter.count. Since the iov_iter is zero-initialized, the copy length is zero and no payload is actually copied to the monitor interface, leaving data un-initialized. Fix this by removing the linear vs non-linear split and using skb_copy_datagram_iter() with iov_iter_kvec() for all cases, as vhost-vsock already does. This handles both linear and non-linear skbs, properly initializes the iov_iter, and removes the now unused virtio_transport_copy_nonlinear_skb(). While touching this code, let's also check the return value of skb_copy_datagram_iter(), even though it's unlikely to fail.
Quoted source text, attributed separately from HOL analysis.