{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74560 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-74560 is a denial of service vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-74560 and fix it if it is affected.\n\nWhat it is: CVE-2026-74560 is a denial of service vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-74560 in the wild and no public exploit code.\n\nAffected product: Linux. 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-74560/ (Markdown: https://insights.sbomify.com/CVE-2026-74560/index.md)","id":"CVE-2026-74560","markdown":"https://insights.sbomify.com/CVE-2026-74560/index.md","name":"CVE-2026-74560","record":{"aliases":["AZL-96315","BELL-CVE-2026-74560","DEBIAN-CVE-2026-74560","GHSA-827x-m92x-hr38","UBUNTU-CVE-2026-74560"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A buffer leak in the Linux kernel's AF_XDP multi-buffer Tx path allows attackers to exhaust memory, causing denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nxsk: fix buffer leak in xsk_drop_skb() for AF_XDP multi-buffer Tx\n\nThis patch is inspired by the check[1] from sashiko. It says when\noverflow happens, the address of cq to be published is invalid.\nActually the severer thing is the whole process of publishing the\naddress of cq in this particular case is not right: it should truely\npublish the address and advance the cached_prod in cq as long as it\nreads descriptors from txq.\n\nThe following is the full analysis.\nxsk_drop_skb() is called in three places, which all discard a partially\nbuilt multi-buffer skb:\n1) xsk_build_skb() -EOVERFLOW error path: packet exceeds MAX_SKB_FRAGS\n2) __xsk_generic_xmit() post-loop cleanup: an invalid descriptor in\n   the TX ring prevents the partial packet from completing\n3) xsk_release(): socket close while xs-\u003eskb holds an incomplete packet\n\nIn all three cases, the TX descriptors for the already-processed frags\nhave been consumed from the TX ring (xskq_cons_release), and CQ slots\nhave been reserved. However, xsk_drop_skb() calls xsk_consume_skb()\nwhich cancels the CQ reservations via xsk_cq_cancel_locked(). Since\nthe buffer addresses never appear in the completion queue, userspace\npermanently loses track of these buffers.\n\nFix this by letting consume_skb() trigger the existing xsk_destruct_skb\ndestructor, which already submits buffer addresses to the CQ via\nxsk_cq_submit_addr_locked().\n\nNote that cancelling the descriptors back to the TX ring (via\nxskq_cons_cancel_n) is not a appropriate option because an oversized\npacket that always exceeds MAX_SKB_FRAGS would be retried indefinitely,\nwhich is an obviously deadlock bug in the TX path.\n\nAlso move the desc-\u003eaddr assignment in xsk_build_skb() above the\noverflow check so that the current descriptor's address is recorded\nbefore a potential -EOVERFLOW jump to free_err, consistent with the\nzerocopy path in xsk_build_skb_zerocopy().\n\n[1]: https://lore.kernel.org/all/20260425041726.85FB3C2BCB2@smtp.kernel.org/","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"xsk: fix buffer leak in xsk_drop_skb() for AF_XDP multi-buffer Tx","id":"CVE-2026-74560","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"nexthop: avoid unlocked f6i_list walk in nh_rt_cache_flush","id":"CVE-2026-74561"},"packages":[],"prev":{"headline":"xsk: drain continuation descs after overflow in xsk_build_skb()","id":"CVE-2026-74559"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A buffer leak in the Linux kernel's AF_XDP multi-buffer Tx path allows attackers to exhaust memory, causing denial of service.","url":"https://insights.sbomify.com/CVE-2026-74560/"}