CVE-2026-74560: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-827x-m92x-hr38
Share
Published
Advisory Summary

CVE-2026-74560 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-74560 at a Glance

CVE Identifier CVE-2026-74560
GHSA Identifier GHSA-827x-m92x-hr38
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-74560

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-74560, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

In the Linux kernel, the following vulnerability has been resolved: xsk: fix buffer leak in xsk_drop_skb() for AF_XDP multi-buffer Tx This patch is inspired by the check[1] from sashiko. It says when overflow happens, the address of cq to be published is invalid. Actually the severer thing is the whole process of publishing the address of cq in this particular case is not right: it should truely publish the address and advance the cached_prod in cq as long as it reads descriptors from txq. The following is the full analysis. xsk_drop_skb() is called in three places, which all discard a partially built multi-buffer skb: 1) xsk_build_skb() -EOVERFLOW error path: packet exceeds MAX_SKB_FRAGS 2) __xsk_generic_xmit() post-loop cleanup: an invalid descriptor in the TX ring prevents the partial packet from completing 3) xsk_release(): socket close while xs->skb holds an incomplete packet In all three cases, the TX descriptors for the already-processed frags have been consumed from the TX ring (xskq_cons_release), and CQ slots have been reserved. However, xsk_drop_skb() calls xsk_consume_skb() which cancels the CQ reservations via xsk_cq_cancel_locked(). Since the buffer addresses never appear in the completion queue, userspace permanently loses track of these buffers. Fix this by letting consume_skb() trigger the existing xsk_destruct_skb destructor, which already submits buffer addresses to the CQ via xsk_cq_submit_addr_locked(). Note that cancelling the descriptors back to the TX ring (via xskq_cons_cancel_n) is not a appropriate option because an oversized packet that always exceeds MAX_SKB_FRAGS would be retried indefinitely, which is an obviously deadlock bug in the TX path. Also move the desc->addr assignment in xsk_build_skb() above the overflow check so that the current descriptor's address is recorded before a potential -EOVERFLOW jump to free_err, consistent with the zerocopy path in xsk_build_skb_zerocopy(). [1]: https://lore.kernel.org/all/20260425041726.85FB3C2BCB2@smtp.kernel.org/

References

NVD — CVE-2026-74560 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-74560
git.kernel.org/stable/c/05e283466b... WEB
https://git.kernel.org/stable/c/05e283466b86e0b25a5209a3eafe87aa9886064a
git.kernel.org/stable/c/a0528ab6af... WEB
https://git.kernel.org/stable/c/a0528ab6af62bf57153caaf8ea28e5fcb0e18fd4
git.kernel.org/stable/c/a3c8382ebc... WEB
https://git.kernel.org/stable/c/a3c8382ebce4780c6b3ace2c09bc342313ac0186

Frequently Asked Questions

What is CVE-2026-74560?
CVE-2026-74560 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-74560?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-74560?
CVE-2026-74560 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-74560?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-827x-m92x-hr38",
  "modified" : "2026-08-15T15:30:36Z",
  "published" : "2026-08-15T15:30:36Z",
  "aliases" : [ "CVE-2026-74560" ],
  "details" : "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->skb 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->addr 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/",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-74560"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/05e283466b86e0b25a5209a3eafe87aa9886064a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a0528ab6af62bf57153caaf8ea28e5fcb0e18fd4"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a3c8382ebce4780c6b3ace2c09bc342313ac0186"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T13:18:01Z"
  }
}