vsock/virtio: fix empty payload in tap skb for non-linear buffers
Summary
| CVE | CVE-2026-46207 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-05-28 10:16:36 UTC |
| Updated | 2026-06-10 19:18:14 UTC |
| 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. |
Risk And Classification
Primary CVSS: v3.1 5.5 MEDIUM from [email protected]
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS: 0.000180000 probability, percentile 0.048040000 (date 2026-06-02)
Problem Types: CWE-401
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Operating System | Linux | Linux Kernel | All | All | All | All |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 4b0bf10eb077cb43c09746251ef3608d62c45667 06747f52ab157591cec7e5623a759473b66ef6f6 git | Not specified |
| CNA | Linux | Linux | affected 4b0bf10eb077cb43c09746251ef3608d62c45667 52da6a74ca3de0fcda60301096b71534b3b18641 git | Not specified |
| CNA | Linux | Linux | affected 4b0bf10eb077cb43c09746251ef3608d62c45667 378b131a25bd1a5ee27ca199fe486c299d5350c5 git | Not specified |
| CNA | Linux | Linux | affected 4b0bf10eb077cb43c09746251ef3608d62c45667 3a3e3d90cbc79600544536723911657730759af3 git | Not specified |
| CNA | Linux | Linux | affected 6.7 | Not specified |
| CNA | Linux | Linux | unaffected 6.7 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.90 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.32 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.0.9 7.0.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1-rc4 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/52da6a74ca3de0fcda60301096b71534b3b18641 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/3a3e3d90cbc79600544536723911657730759af3 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/378b131a25bd1a5ee27ca199fe486c299d5350c5 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/06747f52ab157591cec7e5623a759473b66ef6f6 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.