CVE-2026-72046

Estado: RecibidaCrítica (9.8)—

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:

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.

Leer descripción completaMostrar menos

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:

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.

Detalles técnicos trazas, registros y código del informe original

  - 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)

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.

CVSS

Versión: 3.1
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Puntuación base: 9.8

Probabilidad de explotación (EPSS)

Probabilidad de explotación en los próximos 30 días: 0.67%
Percentil entre todas las CVEs puntuadas: 50
Fecha de la puntuación: 5/10/2026

EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).

🎯 Técnicas ATT&CK

Cómo se explota esta vulnerabilidad y qué consigue el atacante, en el lenguaje de MITRE ATT&CK.

ExplotaciónT1190 Exploit Public-Facing Applicationinitial access75 %
Impacto principalT1499.004 Application or System Exploitationimpact65 %
Impacto secundarioT1565.001 Stored Data Manipulationimpact60 %

Vulnerabilidad remota de corrupción de memoria en kernel Linux (AV:N, PR:N, UI:N) que permite DoS mediante degradación de throughput (T1499.004) y corrupción de datos de paquetes (T1565.001) por indexación incorrecta de buffers con HW-GRO activado.

Inferido por nuestro agente de análisis a partir de la descripción oficial, el vector CVSS y la CWE, y comprobado por un supervisor. Puede contener errores.

🛡️ Mitigaciones ATT&CK que cubren estas técnicas

Filter Network Traffic Vulnerability Scanning Restrict File and Directory Permissions Privileged Account Management Remote Data Storage Network Segmentation

Tecnologías afectadas (1)

⚠ Inferidas por IA a partir de la descripción — NVD aún no ha analizado esta CVE; no son CPE verificados.

Linux — Linux Kernel^AI

Referencias

JSON original (NVD)

Mostrar

{
  "id": "CVE-2026-72046",
  "cveTags": [],
  "metrics": {
    "cvssMetricV31": [
      {
        "type": "Secondary",
        "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "cvssData": {
          "scope": "UNCHANGED",
          "version": "3.1",
          "baseScore": 9.8,
          "attackVector": "NETWORK",
          "baseSeverity": "CRITICAL",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
          "integrityImpact": "HIGH",
          "userInteraction": "NONE",
          "attackComplexity": "LOW",
          "availabilityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "confidentialityImpact": "HIGH"
        },
        "impactScore": 5.9,
        "exploitabilityScore": 3.9
      }
    ]
  },
  "affected": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "affectedData": [
        {
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "product": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5e37d8254e7f551dda62e7590e819d69c7491845",
              "lessThan": "84d3753d4bf284ef770ead6dee2270aaabb3ef41",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "5e37d8254e7f551dda62e7590e819d69c7491845",
              "lessThan": "35267819b25074084130b6a7be18bbaf44d3ae74",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "5e37d8254e7f551dda62e7590e819d69c7491845",
              "lessThan": "9f8e7f59b0c2f466be74bd923726b0f5496c27ad",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "5e37d8254e7f551dda62e7590e819d69c7491845",
              "lessThan": "d676c9a73bdcd8237425dbb826f2bd1a25c36e40",
              "versionType": "git"
            }
          ],
          "programFiles": [
            "drivers/net/ethernet/google/gve/gve_rx_dqo.c"
          ],
          "defaultStatus": "unaffected"
        },
        {
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "product": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.9"
            },
            {
              "status": "unaffected",
              "version": "0",
              "lessThan": "6.9",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "6.12.101",
              "versionType": "semver",
              "lessThanOrEqual": "6.12.*"
            },
            {
              "status": "unaffected",
              "version": "6.18.40",
              "versionType": "semver",
              "lessThanOrEqual": "6.18.*"
            },
            {
              "status": "unaffected",
              "version": "7.1.5",
              "versionType": "semver",
              "lessThanOrEqual": "7.1.*"
            },
            {
              "status": "unaffected",
              "version": "7.2",
              "versionType": "original_commit_for_fix",
              "lessThanOrEqual": "*"
            }
          ],
          "programFiles": [
            "drivers/net/ethernet/google/gve/gve_rx_dqo.c"
          ],
          "defaultStatus": "affected"
        }
      ]
    }
  ],
  "published": "2026-08-15T06:21:13.810",
  "references": [
    {
      "url": "https://git.kernel.org/stable/c/35267819b25074084130b6a7be18bbaf44d3ae74",
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    },
    {
      "url": "https://git.kernel.org/stable/c/84d3753d4bf284ef770ead6dee2270aaabb3ef41",
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    },
    {
      "url": "https://git.kernel.org/stable/c/9f8e7f59b0c2f466be74bd923726b0f5496c27ad",
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    },
    {
      "url": "https://git.kernel.org/stable/c/d676c9a73bdcd8237425dbb826f2bd1a25c36e40",
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "vulnStatus": "Received",
  "descriptions": [
    {
      "lang": "en",
      "value": "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."
    }
  ],
  "lastModified": "2026-08-17T06:18:02.577",
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}