Skip to main content
VulnerabilityPublished Updated

CVE-2026-46207: Linux kernel · vsock/virtio: fix empty payload in tap skb for non-linear buffers

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in 06747f52ab157591cec7e5623a759473b66ef6f6 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:34 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in 06747f52ab157591cec7e5623a759473b66ef6f6, 378b131a25bd1a5ee27ca199fe486c299d5350c5, 52da6a74ca3de0fcda60301096b71534b3b18641 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade Linux kernel to 06747f52ab157591cec7e5623a759473b66ef6f6, 378b131a25bd1a5ee27ca199fe486c299d5350c5, 52da6a74ca3de0fcda60301096b71534b3b18641 or 3a3e3d90cbc79600544536723911657730759af3.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 4b0bf10eb077cb43c09746251ef3608d62c45667, < 06747f52ab157591cec7e5623a759473b66ef6f6
Fixed in
  • 06747f52ab157591cec7e5623a759473b66ef6f6
LinuxLinuxAffected
  • ≥ 4b0bf10eb077cb43c09746251ef3608d62c45667, < 378b131a25bd1a5ee27ca199fe486c299d5350c5
Fixed in
  • 378b131a25bd1a5ee27ca199fe486c299d5350c5
LinuxLinuxAffected
  • ≥ 4b0bf10eb077cb43c09746251ef3608d62c45667, < 52da6a74ca3de0fcda60301096b71534b3b18641
Fixed in
  • 52da6a74ca3de0fcda60301096b71534b3b18641
LinuxLinuxAffected
  • ≥ 4b0bf10eb077cb43c09746251ef3608d62c45667, < 3a3e3d90cbc79600544536723911657730759af3
Fixed in
  • 3a3e3d90cbc79600544536723911657730759af3
LinuxLinuxAffected
  • =6.7
Fixed in–

Description

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.

References

Community reviews

Loading reviews…