CVE-2026-72046: Software Security Vulnerability Vulnerability

CRITICAL
Advisory Identifier: GHSA-9vwj-6q4v-p5m2
CVSS 9.8
Published
Advisory Summary

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

CVE-2026-72046 at a Glance

CVE Identifier CVE-2026-72046
GHSA Identifier GHSA-9vwj-6q4v-p5m2
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 9.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-72046

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-72046, 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: gve: fix header buffer corruption with header-split and HW-GRO The DQO RX datapath programs a per-buffer-queue-descriptor header_buf_addr at post time and reads the split header back at completion time. Both the post and the read currently index the header buffer by queue position rather than by the buffer's identity: - post (gve_rx_post_buffers_dqo): header_buf_addr is computed from bufq->tail - read (gve_rx_dqo): the header is read from desc_idx (the completion queue head index) This relies on the buffer-queue index and the completion-queue index being equal for the start of every packet, i.e. on the device consuming posted buffers and returning completions in the exact same order. That assumption does not hold once HW-GRO is enabled with multiple flows: coalesced segments are accepted and completed in an order that may differ from the order buffers were posted, and segments from different flows may interleave. That results in two problems: 1. Wrong header slot on read. Because the read offset is derived from the completion index (desc_idx) while the device wrote the header to the address programmed for the buffer's buf_id, the driver can copy a header belonging to a different packet. This shows up as throughput drop (about 30% drop and large numbers of TCP retransmissions) with header-split and HW-GRO both enabled and many streams. 2. Header buffer reused while still owned by the device. The driver advances bufq->head by one per completion and re-posts buffers based on that. Arrival of N RX completions only guarantees that at least N RX buffer descriptors have been read by the device. It does not guarantee that the device has relinquished the ownership of all the buffers corresponding to those N descriptors. With out-of-order completions (e.g. the completion for a packet copied into buffer N arrives before the completion for a packet copied into buffer N-1), the driver can re-post and overwrite a header buffer that the device is still going to write into, corrupting the header of a packet whose completion has not yet been processed. Fix both issues by indexing the header buffer by buf_id on both the post and read paths. Reading from buf_id's slot is therefore always correct regardless of completion ordering (fixes problem 1). Indexing by buf_id also ties each header slot to the lifetime of its buffer state. A buffer state is only returned to the free/recycle lists when its own completion (buf_id) is processed, so its header slot can only be re-posted after the device is done with it. This makes header slot reuse safe under out-of-order completions (fixes problem 2). Allocate (gve_rx_alloc_hdr_bufs) and free (gve_rx_free_hdr_bufs) the header buffers based on num_buf_states to match the buf_id indexing.

References

Frequently Asked Questions

What is CVE-2026-72046?
CVE-2026-72046 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-72046?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-72046?
CVE-2026-72046 has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-72046?
CVE-2026-72046 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-72046?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-9vwj-6q4v-p5m2",
  "modified" : "2026-08-17T06:33:06Z",
  "published" : "2026-08-15T06:32:10Z",
  "aliases" : [ "CVE-2026-72046" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ngve: fix header buffer corruption with header-split and HW-GRO\n\nThe DQO RX datapath programs a per-buffer-queue-descriptor\nheader_buf_addr at post time and reads the split header back at\ncompletion time. Both the post and the read currently index the\nheader buffer by queue position rather than by the buffer's identity:\n\n  - post (gve_rx_post_buffers_dqo): header_buf_addr is computed from\n    bufq->tail\n  - read (gve_rx_dqo): the header is read from desc_idx (the completion\n    queue head index)\n\nThis relies on the buffer-queue index and the completion-queue index\nbeing equal for the start of every packet, i.e. on the device consuming\nposted buffers and returning completions in the exact same order. That\nassumption does not hold once HW-GRO is enabled with multiple\nflows: coalesced segments are accepted and completed in an order that\nmay differ from the order buffers were posted, and segments from\ndifferent flows may interleave.\n\nThat results in two problems:\n\n1. Wrong header slot on read. Because the read offset is derived from\n   the completion index (desc_idx) while the device wrote the header to\n   the address programmed for the buffer's buf_id, the driver can copy\n   a header belonging to a different packet. This shows up as\n   throughput drop (about 30% drop and large numbers of TCP\n   retransmissions) with header-split and HW-GRO both enabled and many\n   streams.\n\n2. Header buffer reused while still owned by the device. The driver\n   advances bufq->head by one per completion and re-posts buffers based\n   on that. Arrival of N RX completions only guarantees that at least N\n   RX buffer descriptors have been read by the device. It does not\n   guarantee that the device has relinquished the ownership of all the\n   buffers corresponding to those N descriptors. With out-of-order\n   completions (e.g. the completion for a packet copied into buffer N\n   arrives before the completion for a packet copied into buffer N-1),\n   the driver can re-post and overwrite a header buffer that the device\n   is still going to write into, corrupting the header of a packet\n   whose completion has not yet been processed.\n\nFix both issues by indexing the header buffer by buf_id on both the post\nand read paths. Reading from buf_id's slot is therefore always correct\nregardless of completion ordering (fixes problem 1).\n\nIndexing by buf_id also ties each header slot to the lifetime of its\nbuffer state. A buffer state is only returned to the free/recycle lists\nwhen its own completion (buf_id) is processed, so its header slot can\nonly be re-posted after the device is done with it. This makes header\nslot reuse safe under out-of-order completions (fixes problem 2).\n\nAllocate (gve_rx_alloc_hdr_bufs) and free (gve_rx_free_hdr_bufs) the\nheader buffers based on num_buf_states to match the buf_id indexing.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72046"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/35267819b25074084130b6a7be18bbaf44d3ae74"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/84d3753d4bf284ef770ead6dee2270aaabb3ef41"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9f8e7f59b0c2f466be74bd923726b0f5496c27ad"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d676c9a73bdcd8237425dbb826f2bd1a25c36e40"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "CRITICAL",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:21:13Z"
  }
}