CVE-2026-53365Linux Linux Kernel
NVDCVSS scored by NVD (NIST)
Vulnerability Summary
In the Linux kernel, the following vulnerability has been resolved:
vsock/virtio: fix zerocopy completion for multi-skb sends
When a large message is fragmented into multiple skbs, the zerocopy
uarg is only allocated and attached to the last skb in the loop.
Non-final skbs carry pinned user pages with no completion tracking,
so the kernel has no way to notify userspace when those pages are safe
to reuse. If the loop breaks early the uarg is never allocated at all,
leaking pinned pages with no completion notification.
Fix this by following the approach used by TCP: allocate the zerocopy
uarg (if not provided by the caller) before the send loop and attach
it to every skb via skb_zcopy_set(), which takes a reference per skb.
Each skb's completion properly decrements the refcount, and the
notification only fires after the last skb is freed.
On failure, if no data was sent, the uarg is cleanly aborted via
net_zcopy_put_abort().
This issue was initially discovered by sashiko while reviewing commit
1cb36e252211 ("vsock/virtio: fix MSG_ZEROCOPY pinned-pages accounting")
but was pre-existing.
vsock/virtio: fix zerocopy completion for multi-skb sends
When a large message is fragmented into multiple skbs, the zerocopy
uarg is only allocated and attached to the last skb in the loop.
Non-final skbs carry pinned user pages with no completion tracking,
so the kernel has no way to notify userspace when those pages are safe
to reuse. If the loop breaks early the uarg is never allocated at all,
leaking pinned pages with no completion notification.
Fix this by following the approach used by TCP: allocate the zerocopy
uarg (if not provided by the caller) before the send loop and attach
it to every skb via skb_zcopy_set(), which takes a reference per skb.
Each skb's completion properly decrements the refcount, and the
notification only fires after the last skb is freed.
On failure, if no data was sent, the uarg is cleanly aborted via
net_zcopy_put_abort().
This issue was initially discovered by sashiko while reviewing commit
1cb36e252211 ("vsock/virtio: fix MSG_ZEROCOPY pinned-pages accounting")
but was pre-existing.
CVSS v3.1 Base Metrics — Score 5.5 (MEDIUM)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HAttack VectorLocal
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityNone
AvailabilityHigh
Affected & Patched Versions
- Linux Linux Kernel >= 6.7 and < 6.18.34
- Linux Linux Kernel >= 6.19 and < 7.0.11
- Linux Linux Kernel
- Linux Linux Kernel 6.18.34
- Linux Linux Kernel 7.0.11
What to do
Fix it during your normal patch cycle. No exploitation is confirmed yet.
- Check whether you run Linux Linux Kernel and which version.
- Update to a patched version listed above, then confirm the new version.
Timeline
- Jul 13, 2026Published
- Aug 18, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new Linux Linux Kernel CVEsYou are reading CVE-2026-53365. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsExternal References
- Referencehttps://git.kernel.org/stable/c/293fe8f2d1b5ac464ca16a8eba09571bbbb34ba9
- Patchhttps://git.kernel.org/stable/c/76b995bc57bd90cb6e954e1966fbd8786da47f0d
- Patchhttps://git.kernel.org/stable/c/ae38d9179190a956e2a87a69ef1dd6f451b51c4d
- Patchhttps://git.kernel.org/stable/c/b3155f2b78db21e99256bcf7eb902f24ff6d5338
- Referencehttps://github.com/MaherAzzouzi/vsockdrop
Data last checked: Nov 17, 2026 19:13 UTC