{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53365 exists.","fix":"Apply the vendor's patch.","what":"CVE-2026-53365 is a high-severity denial of service vulnerability in Linux kernel, published on 13 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-53365 and fix it if it is affected.\n\nWhat it is: CVE-2026-53365 is a high-severity denial of service vulnerability in Linux kernel, published on 13 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53365 exists.\n\nAffected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-53365/ (Markdown: https://insights.sbomify.com/CVE-2026-53365/index.md)","id":"CVE-2026-53365","markdown":"https://insights.sbomify.com/CVE-2026-53365/index.md","name":"CVE-2026-53365","record":{"aliases":["BELL-CVE-2026-53365","DEBIAN-CVE-2026-53365","GHSA-9p63-4jq7-2c9w","ROOT-OS-DEBIAN-13-CVE-2026-53365","ROOT-OS-UBUNTU-2404-CVE-2026-53365","UBUNTU-CVE-2026-53365"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel vsock","requires_auth":"low_privilege","summary":"A flaw in Linux kernel vsock/virtio zerocopy handling leaks pinned pages, potentially causing memory exhaustion and denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-401","name":"Missing Release of Memory after Effective Lifetime"},{"id":"CWE-404","name":"Improper Resource Shutdown or Release"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-08-14","github_poc":3,"max_poc_stars":5,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-08-19T12:26:19Z","kind":"github_poc","ref":"https://github.com/HackSpeak/CVE-2026-53365","stars":5,"title":"VsockDrop (CVE-2026-53365) Linux kernel io_uring zerocopy vsock LPE exploit mirror — MaherAzzouzi, MIT; for authorized security testing"},{"date":"2026-08-14T15:12:49Z","kind":"github_poc","ref":"https://github.com/HORKimhab/CVE-2026-53365","stars":0,"title":"CVE-2026-53365"},{"date":"2026-10-16T00:40:34Z","kind":"github_poc","ref":"https://github.com/hoodoer/VsockDrop-Adapted-CVE-2026-53365","stars":0,"title":"A slightly more robust version of MaherAzzouzi's POC, created by my agent on the fly during testing. "}],"tier":"weaponised"},"has_fix":true,"headline":"vsock/virtio: fix zerocopy completion for multi-skb sends","id":"CVE-2026-53365","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"ipv4: account for fraggap on the paged allocation path","id":"CVE-2026-53366"},"packages":[],"prev":{"headline":"Bluetooth: hci_conn: Fix memory leak in hci_le_big_terminate()","id":"CVE-2026-53364"},"products":["Linux"],"published":"2026-07-13","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-18","vendors":["Linux"]},"summary":"A flaw in Linux kernel vsock/virtio zerocopy handling leaks pinned pages, potentially causing memory exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2026-53365/"}