CVE-2026-64121: net: ifb: report ethtool stats over num_tx_queues
High 7.1 EPSS 0.1% Linux kernel
In the Linux kernel, the following vulnerability has been resolved: net: ifb: report ethtool stats over num_tx_queues ifb_dev_init() allocates dp->tx_private to dev->num_tx_queues entries via kzalloc_objs(*txp, dev->num_tx_queues). Both IFB per-queue RX and TX stats live in those entries: ifb_xmit() updates txp->rx_stats using the skb queue mapping, ifb_ri_tasklet() updates txp->tx_stats, and ifb_stats64() aggregates both over dev->num_tx_queues. The ethtool stats callbacks instead size and walk the per-queue stats with dev->real_num_rx_queues and dev->real_num_tx_queues. With an asymmetric device where the RX queue count exceeds the TX queue count, for example: ip link add name ifb10 numtxqueues 1 numrxqueues 8 type ifb ethtool -S ifb10 ifb_get_ethtool_stats() indexes past the tx_private allocation and copies adjacent slab data through ETHTOOL_GSTATS. Use dev->num_tx_queues consistently for the stats strings, the stats count, and the stats data walks. This reports one RX stats group and one TX stats group for each backing ifb_q_private entry, which is the queue set IFB can actually populate. Reproduced under UML+KASAN at v7.1-rc2: BUG: KASAN: slab-out-of-bounds in ifb_fill_stats_data+0x3c/0xae Read of size 8 at addr 0000000062dbd228 by task ethtool/36 ifb_fill_stats_data+0x3c/0xae ifb_get_ethtool_stats+0xc0/0x129 __dev_ethtool+0x1ca5/0x363c dev_ethtool+0x123/0x1b3 dev_ioctl+0x56c/0x744 sock_do_ioctl+0x15f/0x1b2 sock_ioctl+0x4d5/0x50a sys_ioctl+0xd8b/0xde9 With the patch applied, the same UML+KASAN repro is silent and ethtool -S ifb10 reports only the stats backed by the single allocated tx_private entry.
- CVE-2026-64121CVE identifier
- 7.1CVSS 3.1 base score (high)
- 0.1%EPSS: chance of exploitation in the next 30 days (higher than 2% of CVEs)
- 2026-07-19published
What do these terms mean? CVE · CVSS score · exploited (KEV) · EPSS · backported fix · all terms
What to do now
- Check whether you run Linux kernel and which version (commands below).
- Install the fixed version for your system: see “Patch it” below.
- Reboot into the new kernel (uname -r to confirm); live patching (kpatch, Ubuntu Livepatch, SUSE kGraft/klp) can defer the reboot for some CVEs
Affected and fixed versions
Affected:
- Linux Linux a21ee5b2fcb8d6d3973446c5039e966c4cfe40d1 to before 6afdb8113cb007f9332f59a9b7fd45731b8a9de5
- Linux Linux a21ee5b2fcb8d6d3973446c5039e966c4cfe40d1 to before 16bd798cb6d8337d7c3eea1adc412f31b5181d5b
- Linux Linux a21ee5b2fcb8d6d3973446c5039e966c4cfe40d1 to before 301a554e458e2f5ec47f2c336a7cb03b877f9fd6
- Linux Linux a21ee5b2fcb8d6d3973446c5039e966c4cfe40d1 to before f8a5a76b4a683043c6eff2a060bcaa17f9316ad5
- Linux Linux a21ee5b2fcb8d6d3973446c5039e966c4cfe40d1 to before 2638e1773904d7aa8f24c6e7fda2ed7d69df6fa4
- Linux Linux a21ee5b2fcb8d6d3973446c5039e966c4cfe40d1 to before 5db89c99566fc4728cc92e941d8e1975711e24b5
- Linux Linux 5.17
Patch it
Use the commands for your system. Distribution packages often keep an older version number with the fix backported, so compare with the fixed package versions in the table below, not only with the upstream version.
Debian
sudo apt update
sudo apt install --only-upgrade linux-image-amd64Ubuntu
sudo apt update
sudo apt install --only-upgrade linux-image-generic (or the installed flavour: linux-image-aws, -azure, -gcp, -virtual)RHEL, AlmaLinux, Rocky, Oracle
sudo dnf upgrade --refresh kernelFedora
sudo dnf upgrade --refresh kernelSUSE / openSUSE
sudo zypper refresh
sudo zypper update kernel-defaultAmazon Linux
sudo dnf upgrade --releasever=latest kernel kernel6.12Arch Linux
sudo pacman -SyuAlpine
apk update && apk upgrade linux-lts linux-virtFreeBSD
not LinuxGeneral update steps for every system are on the Linux and Unix & BSD pages; after updating, see which services to restart.
Fix status in Linux distributions
| Release | Package | Status | Fixed version / advisory |
|---|---|---|---|
| Debian 12 | linux | fixed | 6.1.176-1 |
| Debian 13 | linux | fixed | 6.12.94-1 |
| Debian testing | linux | fixed | 7.0.12-1 |
| Red Hat Enterprise Linux 9 | kernel | fix deferred | |
| Red Hat Enterprise Linux 6 | kernel | out of support scope | |
| Red Hat Enterprise Linux 10 | kernel | fix deferred | |
From the Debian security tracker, Ubuntu CVE tracker and Red Hat Security Data API, refreshed every few hours.
Sources
- https://git.kernel.org/stable/c/6afdb8113cb007f9332f59a9b7fd45731b8a9de5
- https://git.kernel.org/stable/c/16bd798cb6d8337d7c3eea1adc412f31b5181d5b
- https://git.kernel.org/stable/c/301a554e458e2f5ec47f2c336a7cb03b877f9fd6
- https://git.kernel.org/stable/c/f8a5a76b4a683043c6eff2a060bcaa17f9316ad5
- https://git.kernel.org/stable/c/2638e1773904d7aa8f24c6e7fda2ed7d69df6fa4
- https://git.kernel.org/stable/c/5db89c99566fc4728cc92e941d8e1975711e24b5
- CVE-2026-64121 on CVE.org
- CVE-2026-64121 on NVD
Page generated automatically from official sources on 2026-11-03 18:05 UTC. Always confirm with your vendor's advisory.