CVE-2026-64035 (GCVE-0-2026-64035)
Vulnerability from cvelistv5
Published
2026-07-19 15:39
Modified
2026-10-19 20:28
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: igc: set tx buffer type for SMD frames Sashiko pointed out that igc_fpe_init_smd_frame() initializes igc_tx_buffer fields for an SMD skb, but does not set the buffer type: https://sashiko.dev/#/patchset/20260415025226.114115-1-kohei%40enjuk.jp Since igc_tx_buffer entries are reused, a stale XDP or XSK type can remain and make TX completion use the wrong cleanup path. Set the buffer type to IGC_TX_BUFFER_TYPE_SKB.
Impacted products
Vendor Product Version
Linux Linux Version: 5422570c0010bb968738f9256eb2bf83e79b4d63
Version: 5422570c0010bb968738f9256eb2bf83e79b4d63
Version: 5422570c0010bb968738f9256eb2bf83e79b4d63
Create a notification for this product.
Show details on NVD website


{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-64035",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "yes"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-10-16T15:35:44.841022Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "problemTypes": [
          {
            "descriptions": [
              {
                "cweId": "CWE-665",
                "description": "CWE-665 Improper Initialization",
                "lang": "en",
                "type": "CWE"
              }
            ]
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-10-19T20:28:10.044Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/net/ethernet/intel/igc/igc_tsn.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "1f83545f432d106d5fc71d3997b2d382104ebcc4",
              "status": "affected",
              "version": "5422570c0010bb968738f9256eb2bf83e79b4d63",
              "versionType": "git"
            },
            {
              "lessThan": "1c8587bd025244aa52061f5ceecbf5e68a1063d9",
              "status": "affected",
              "version": "5422570c0010bb968738f9256eb2bf83e79b4d63",
              "versionType": "git"
            },
            {
              "lessThan": "5acc641e590e008caaed480ed9ffae47cf7ecbdf",
              "status": "affected",
              "version": "5422570c0010bb968738f9256eb2bf83e79b4d63",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/net/ethernet/intel/igc/igc_tsn.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.16"
            },
            {
              "lessThan": "6.16",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.34",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.0.*",
              "status": "unaffected",
              "version": "7.0.11",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.34",
                  "versionStartIncluding": "6.16",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0.11",
                  "versionStartIncluding": "6.16",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1",
                  "versionStartIncluding": "6.16",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 9.8,
            "baseSeverity": "CRITICAL",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "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."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T12:38:29.607Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/1f83545f432d106d5fc71d3997b2d382104ebcc4"
        },
        {
          "url": "https://git.kernel.org/stable/c/1c8587bd025244aa52061f5ceecbf5e68a1063d9"
        },
        {
          "url": "https://git.kernel.org/stable/c/5acc641e590e008caaed480ed9ffae47cf7ecbdf"
        }
      ],
      "title": "igc: set tx buffer type for SMD frames",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-64035",
    "datePublished": "2026-07-19T15:39:24.128Z",
    "dateReserved": "2026-07-19T07:54:57.028Z",
    "dateUpdated": "2026-10-19T20:28:10.044Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2026-64035\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"yes\"}, {\"Technical Impact\": \"total\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-10-16T15:35:44.841022Z\"}}}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-665\", \"description\": \"CWE-665 Improper Initialization\"}]}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-10-16T15:35:45.613Z\"}}], \"cna\": {\"title\": \"igc: set tx buffer type for SMD frames\", \"metrics\": [{\"cvssV3_1\": {\"version\": \"3.1\", \"baseScore\": 9.8, \"baseSeverity\": \"CRITICAL\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"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.\"}]}], \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"5422570c0010bb968738f9256eb2bf83e79b4d63\", \"lessThan\": \"1f83545f432d106d5fc71d3997b2d382104ebcc4\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"5422570c0010bb968738f9256eb2bf83e79b4d63\", \"lessThan\": \"1c8587bd025244aa52061f5ceecbf5e68a1063d9\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"5422570c0010bb968738f9256eb2bf83e79b4d63\", \"lessThan\": \"5acc641e590e008caaed480ed9ffae47cf7ecbdf\", \"versionType\": \"git\"}], \"programFiles\": [\"drivers/net/ethernet/intel/igc/igc_tsn.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.16\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"6.16\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"6.18.34\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.18.*\"}, {\"status\": \"unaffected\", \"version\": \"7.0.11\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"7.0.*\"}, {\"status\": \"unaffected\", \"version\": \"7.1\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"drivers/net/ethernet/intel/igc/igc_tsn.c\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/1f83545f432d106d5fc71d3997b2d382104ebcc4\"}, {\"url\": \"https://git.kernel.org/stable/c/1c8587bd025244aa52061f5ceecbf5e68a1063d9\"}, {\"url\": \"https://git.kernel.org/stable/c/5acc641e590e008caaed480ed9ffae47cf7ecbdf\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"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.\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.18.34\", \"versionStartIncluding\": \"6.16\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"7.0.11\", \"versionStartIncluding\": \"6.16\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"7.1\", \"versionStartIncluding\": \"6.16\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2026-08-05T12:38:29.607Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2026-64035\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-10-19T20:28:10.044Z\", \"dateReserved\": \"2026-07-19T07:54:57.028Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2026-07-19T15:39:24.128Z\", \"assignerShortName\": \"Linux\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…