{"api_version":"1","generated_at":"2026-07-15T03:58:05+00:00","cve":"CVE-2026-53365","urls":{"html":"https://cve.report/CVE-2026-53365","api":"https://cve.report/api/cve/CVE-2026-53365.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-53365","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-53365"},"summary":{"title":"vsock/virtio: fix zerocopy completion for multi-skb sends","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nvsock/virtio: fix zerocopy completion for multi-skb sends\n\nWhen a large message is fragmented into multiple skbs, the zerocopy\nuarg is only allocated and attached to the last skb in the loop.\nNon-final skbs carry pinned user pages with no completion tracking,\nso the kernel has no way to notify userspace when those pages are safe\nto reuse. If the loop breaks early the uarg is never allocated at all,\nleaking pinned pages with no completion notification.\n\nFix this by following the approach used by TCP: allocate the zerocopy\nuarg (if not provided by the caller) before the send loop and attach\nit to every skb via skb_zcopy_set(), which takes a reference per skb.\nEach skb's completion properly decrements the refcount, and the\nnotification only fires after the last skb is freed.\nOn failure, if no data was sent, the uarg is cleanly aborted via\nnet_zcopy_put_abort().\n\nThis issue was initially discovered by sashiko while reviewing commit\n1cb36e252211 (\"vsock/virtio: fix MSG_ZEROCOPY pinned-pages accounting\")\nbut was pre-existing.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-07-13 18:16:28","updated_at":"2026-07-14 15:26:52"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/b3155f2b78db21e99256bcf7eb902f24ff6d5338","name":"https://git.kernel.org/stable/c/b3155f2b78db21e99256bcf7eb902f24ff6d5338","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/76b995bc57bd90cb6e954e1966fbd8786da47f0d","name":"https://git.kernel.org/stable/c/76b995bc57bd90cb6e954e1966fbd8786da47f0d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/ae38d9179190a956e2a87a69ef1dd6f451b51c4d","name":"https://git.kernel.org/stable/c/ae38d9179190a956e2a87a69ef1dd6f451b51c4d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-53365","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53365","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 581512a6dc939ef122e49336626ae159f3b8a345 76b995bc57bd90cb6e954e1966fbd8786da47f0d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 581512a6dc939ef122e49336626ae159f3b8a345 b3155f2b78db21e99256bcf7eb902f24ff6d5338 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 581512a6dc939ef122e49336626ae159f3b8a345 ae38d9179190a956e2a87a69ef1dd6f451b51c4d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.7","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.7 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.34 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0.11 7.0.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"53365","cve":"CVE-2026-53365","epss":"0.001550000","percentile":"0.050800000","score_date":"2026-07-14","updated_at":"2026-07-15 00:14:55"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["net/vmw_vsock/virtio_transport_common.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"76b995bc57bd90cb6e954e1966fbd8786da47f0d","status":"affected","version":"581512a6dc939ef122e49336626ae159f3b8a345","versionType":"git"},{"lessThan":"b3155f2b78db21e99256bcf7eb902f24ff6d5338","status":"affected","version":"581512a6dc939ef122e49336626ae159f3b8a345","versionType":"git"},{"lessThan":"ae38d9179190a956e2a87a69ef1dd6f451b51c4d","status":"affected","version":"581512a6dc939ef122e49336626ae159f3b8a345","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["net/vmw_vsock/virtio_transport_common.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.7"},{"lessThan":"6.7","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.34","versionType":"semver"},{"lessThanOrEqual":"7.0.*","status":"unaffected","version":"7.0.11","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.34","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0.11","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1","versionStartIncluding":"6.7","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nvsock/virtio: fix zerocopy completion for multi-skb sends\n\nWhen a large message is fragmented into multiple skbs, the zerocopy\nuarg is only allocated and attached to the last skb in the loop.\nNon-final skbs carry pinned user pages with no completion tracking,\nso the kernel has no way to notify userspace when those pages are safe\nto reuse. If the loop breaks early the uarg is never allocated at all,\nleaking pinned pages with no completion notification.\n\nFix this by following the approach used by TCP: allocate the zerocopy\nuarg (if not provided by the caller) before the send loop and attach\nit to every skb via skb_zcopy_set(), which takes a reference per skb.\nEach skb's completion properly decrements the refcount, and the\nnotification only fires after the last skb is freed.\nOn failure, if no data was sent, the uarg is cleanly aborted via\nnet_zcopy_put_abort().\n\nThis issue was initially discovered by sashiko while reviewing commit\n1cb36e252211 (\"vsock/virtio: fix MSG_ZEROCOPY pinned-pages accounting\")\nbut was pre-existing."}],"providerMetadata":{"dateUpdated":"2026-07-13T17:33:52.863Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/76b995bc57bd90cb6e954e1966fbd8786da47f0d"},{"url":"https://git.kernel.org/stable/c/b3155f2b78db21e99256bcf7eb902f24ff6d5338"},{"url":"https://git.kernel.org/stable/c/ae38d9179190a956e2a87a69ef1dd6f451b51c4d"}],"title":"vsock/virtio: fix zerocopy completion for multi-skb sends","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-53365","datePublished":"2026-07-13T17:33:52.863Z","dateReserved":"2026-06-09T07:44:35.400Z","dateUpdated":"2026-07-13T17:33:52.863Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-07-13 18:16:28","lastModifiedDate":"2026-07-14 15:26:52","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"53365","Ordinal":"1","Title":"vsock/virtio: fix zerocopy completion for multi-skb sends","CVE":"CVE-2026-53365","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"53365","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nvsock/virtio: fix zerocopy completion for multi-skb sends\n\nWhen a large message is fragmented into multiple skbs, the zerocopy\nuarg is only allocated and attached to the last skb in the loop.\nNon-final skbs carry pinned user pages with no completion tracking,\nso the kernel has no way to notify userspace when those pages are safe\nto reuse. If the loop breaks early the uarg is never allocated at all,\nleaking pinned pages with no completion notification.\n\nFix this by following the approach used by TCP: allocate the zerocopy\nuarg (if not provided by the caller) before the send loop and attach\nit to every skb via skb_zcopy_set(), which takes a reference per skb.\nEach skb's completion properly decrements the refcount, and the\nnotification only fires after the last skb is freed.\nOn failure, if no data was sent, the uarg is cleanly aborted via\nnet_zcopy_put_abort().\n\nThis issue was initially discovered by sashiko while reviewing commit\n1cb36e252211 (\"vsock/virtio: fix MSG_ZEROCOPY pinned-pages accounting\")\nbut was pre-existing.","Type":"Description","Title":"vsock/virtio: fix zerocopy completion for multi-skb sends"}]}}}