{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-64035",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-64035"
  ],
  "published": "2026-07-19T15:41:06Z",
  "summary": "igc: set tx buffer type for SMD frames",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nigc: set tx buffer type for SMD frames\n\nSashiko pointed out that igc_fpe_init_smd_frame() initializes\nigc_tx_buffer fields for an SMD skb, but does not set the buffer type:\nhttps://sashiko.dev/#/patchset/20260415025226.114115-1-kohei%40enjuk.jp\n\nSince igc_tx_buffer entries are reused, a stale XDP or XSK type can\nremain and make TX completion use the wrong cleanup path.\n\nSet the buffer type to IGC_TX_BUFFER_TYPE_SKB.",
  "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": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:13",
        "name": "linux"
      },
      "versions": [
        "1:6.18.29-1+rpt1",
        "1:6.18.33-1+rpt1"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-2712",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-v8",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-v8-rt",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-2712",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-v8",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-v8-rt",
            "binary_version": "1:6.18.33-1+rpt1"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.18.29-1+rpt1": {
            "linux_commit": "66318c5b5cd8145a662303af12ed39ac07eb27cc",
            "upstream_version": "6.18.29",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.18.34"
          },
          "1:6.18.33-1+rpt1": {
            "linux_commit": "95b85bebbedcaedfa7ca79116ed38b7376fba412",
            "upstream_version": "6.18.33",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.18.34"
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-64035"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/1f83545f432d106d5fc71d3997b2d382104ebcc4"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/1c8587bd025244aa52061f5ceecbf5e68a1063d9"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/5acc641e590e008caaed480ed9ffae47cf7ecbdf"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-05T13:16:28Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 9.8,
      "cvss_v3_severity": "Critical",
      "scenario": "AV:N - The vulnerable TX completion path is reached when the igc driver receives an Ethernet SMD-V/SMD-R mPacket from a link partner and automatically transmits an SMD response frame; this is a network-delivered L2 frame processed in the RX/NAPI path per kernel network-reachability guidance.\nAC:L - Once FPE/pMAC is enabled on the target, an attacker can repeatedly inject SMD-V frames to trigger SMD-R transmissions and race ring-slot reuse; stale XDP/XSK buffer types persist after prior transmissions on the same queue index, making reliable triggering feasible without conditions outside attacker influence.\nPR:N - Exploitation requires only the ability to send Ethernet frames to a host that already has FPE/pMAC administratively enabled (expected in TSN/industrial deployments); the attacker does not need local accounts, CAP_NET_ADMIN, or any authenticated session to reach the vulnerable code path.\nUI:N - No victim interaction is required; SMD response transmission and the resulting erroneous TX cleanup occur automatically in interrupt/NAPI context in response to attacker-supplied link-layer frames.\nS:U - Impact is confined to kernel memory corruption and privilege escalation within the same kernel security domain; this is not a VM escape, IOMMU bypass, or cross-authority sandbox breakout.\nC:H - Stale XDP buffer typing causes `xdp_return_frame()` to interpret an `sk_buff` pointer as an `xdp_frame`, a type confusion that reads attacker-influenced structure fields and can yield arbitrary kernel memory disclosure primitives.\nI:H - The wrong TX cleanup path performs improper `xdp_return_frame()`/`__xdp_return()` operations on mis-typed memory, enabling heap corruption and exploitable control-flow or arbitrary-write primitives typical of kernel type-confusion bugs.\nA:H - Mis-typed TX buffer cleanup can immediately kernel-oops or panic via invalid page-pool returns, and repeated triggering leaks SKBs/DMA mappings causing sustained denial of service on the affected interface or host."
    }
  }
}