From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-64035: igc: set tx buffer type for SMD frames
Date: Sun, 19 Jul 2026 17:38:17 +0200 [thread overview]
Message-ID: <2026071905-CVE-2026-64035-207f@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
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.
The Linux kernel CVE team has assigned CVE-2026-64035 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.16 with commit 5422570c0010bb968738f9256eb2bf83e79b4d63 and fixed in 6.18.34 with commit 1f83545f432d106d5fc71d3997b2d382104ebcc4
Issue introduced in 6.16 with commit 5422570c0010bb968738f9256eb2bf83e79b4d63 and fixed in 7.0.11 with commit 1c8587bd025244aa52061f5ceecbf5e68a1063d9
Issue introduced in 6.16 with commit 5422570c0010bb968738f9256eb2bf83e79b4d63 and fixed in 7.1 with commit 5acc641e590e008caaed480ed9ffae47cf7ecbdf
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-64035
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/net/ethernet/intel/igc/igc_tsn.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/1f83545f432d106d5fc71d3997b2d382104ebcc4
https://git.kernel.org/stable/c/1c8587bd025244aa52061f5ceecbf5e68a1063d9
https://git.kernel.org/stable/c/5acc641e590e008caaed480ed9ffae47cf7ecbdf
reply other threads:[~2026-07-19 15:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026071905-CVE-2026-64035-207f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox