CVE-2026-80779

What the bug is

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.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

drivers/net/ethernet/pensando/ionic/ionic_lif.c
drivers/net/ethernet/pensando/ionic/ionic_txrx.c

What this is

PENSANDO ETHERNET DRIVERSMAINTAINERS section matched on drivers/net/ethernet/pensando/ · netdev@vger.kernel.org · Maintained

Kernel module

ionic

Check it on the machine

grep -wE 'CONFIG_ETHERNET|CONFIG_IONIC|CONFIG_NET_VENDOR_PENSANDO' /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

lsmod | grep -w ionic

Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.

Show whether Debian builds this, per release

Debian does not build this code in 1 release. It does build it in 4 releases, so the answer depends on which release the machine runs.

• bookwormn
• trixieMnot built on armel/rpi, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp
• forky, sidMnot built on armhf/armmp, armhf/armmp-lpae
• bookworm · linux-6.12Mnot built on armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp

n

not enabled on any flavour - this release does not build the code

M

a module where it is built at all; some flavours do not build it

Build switches

CONFIG_ETHERNET, CONFIG_IONIC, CONFIG_NET_VENDOR_PENSANDO

Reads as

all on means the file is compiled; any one off means it is not.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published

2026-09-04 (44 days ago)source

CVSS

no vector published, unrated

Attack vector

not published

EPSS

0.17%, higher than 5.7% of all CVEssource

CISA KEV

not listedthe KEV catalogue

Debian urgency

unimportantsource

Subsystem

drivers/net

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

Introduced	Fixed in	Commit
6.9	6.12.106	881a805a8029
6.9	6.18.47	39fc615e355b
6.9	7.1.11	f3868046e8e2
6.9	7.2.1	ea081b443551
6.9	7.3	d92255b405fb

Debian advisories