From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80779: net/ionic: avoid OOB TX partner lookup for hwstamp RXQ
Date: Fri, 4 Sep 2026 17:11:18 +0200 [thread overview]
Message-ID: <2026090403-CVE-2026-80779-df63@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net/ionic: avoid OOB TX partner lookup for hwstamp RXQ
The dedicated hardware timestamp RX queue is allocated with q->index
equal to lif->ionic->nrxqs_per_lif. The normal txqcqs array only
contains the regular queue pairs, so using that index to set rxq->partner
can read one entry past txqcqs[] and then write through the derived
pointer.
Only link RX/TX partners for normal queue-pair indexes. Leave the hwstamp
RX queue unpaired, and make the XDP_TX path abort cleanly if an RX queue
has no TX partner.
The Linux kernel CVE team has assigned CVE-2026-80779 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.9 with commit 8eeed8373e1cca836799bf8e4a05cffa8e444908 and fixed in 6.12.106 with commit 881a805a8029ba48c0ce81c6674910f8d83f7afb
Issue introduced in 6.9 with commit 8eeed8373e1cca836799bf8e4a05cffa8e444908 and fixed in 6.18.47 with commit 39fc615e355b65b8d43be30da57aa95ae6eaf688
Issue introduced in 6.9 with commit 8eeed8373e1cca836799bf8e4a05cffa8e444908 and fixed in 7.1.11 with commit f3868046e8e2e761d4d943a232bd109ff22a7d5b
Issue introduced in 6.9 with commit 8eeed8373e1cca836799bf8e4a05cffa8e444908 and fixed in 7.2.1 with commit ea081b4435515ac7177eb598a3c0678d1b9e7911
Issue introduced in 6.9 with commit 8eeed8373e1cca836799bf8e4a05cffa8e444908 and fixed in 7.3-rc1 with commit d92255b405fb6f5acca408239ccd742e0a42c9cb
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-80779
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/pensando/ionic/ionic_lif.c
drivers/net/ethernet/pensando/ionic/ionic_txrx.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/881a805a8029ba48c0ce81c6674910f8d83f7afb
https://git.kernel.org/stable/c/39fc615e355b65b8d43be30da57aa95ae6eaf688
https://git.kernel.org/stable/c/f3868046e8e2e761d4d943a232bd109ff22a7d5b
https://git.kernel.org/stable/c/ea081b4435515ac7177eb598a3c0678d1b9e7911
https://git.kernel.org/stable/c/d92255b405fb6f5acca408239ccd742e0a42c9cb
reply other threads:[~2026-09-04 15:15 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=2026090403-CVE-2026-80779-df63@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.