CVE-2026-64121
CVE.org · Published
- Record status
- Published
- Identifier year (not publication year)
- 2026
- Source publication
- Source updated
- Imported by cveboard
- Source snapshot
- cve_2026-10-24_midnight_baseline ·
CNA source text (English)
net: ifb: report ethtool stats over num_tx_queues
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.
Scoped product and version facts
Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.
Exploitation unknown; this catalogue does not assess exploitation.
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
unaffected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| a21ee5b2fcb8d6d3973446c5039e966c4cfe40d1 | affected | git | 6afdb8113cb007f9332f59a9b7fd45731b8a9de5 | Unavailable | None listed |
| a21ee5b2fcb8d6d3973446c5039e966c4cfe40d1 | affected | git | 16bd798cb6d8337d7c3eea1adc412f31b5181d5b | Unavailable | None listed |
| a21ee5b2fcb8d6d3973446c5039e966c4cfe40d1 | affected | git | 301a554e458e2f5ec47f2c336a7cb03b877f9fd6 | Unavailable | None listed |
| a21ee5b2fcb8d6d3973446c5039e966c4cfe40d1 | affected | git | f8a5a76b4a683043c6eff2a060bcaa17f9316ad5 | Unavailable | None listed |
| a21ee5b2fcb8d6d3973446c5039e966c4cfe40d1 | affected | git | 2638e1773904d7aa8f24c6e7fda2ed7d69df6fa4 | Unavailable | None listed |
| a21ee5b2fcb8d6d3973446c5039e966c4cfe40d1 | affected | git | 5db89c99566fc4728cc92e941d8e1975711e24b5 | Unavailable | None listed |
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
affected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 5.17 | affected | Unavailable | Unavailable | Unavailable | None listed |
| 0 | unaffected | semver | 5.17 | Unavailable | None listed |
| 6.1.175 | unaffected | semver | Unavailable | 6.1.* | None listed |
| 6.6.142 | unaffected | semver | Unavailable | 6.6.* | None listed |
| 6.12.92 | unaffected | semver | Unavailable | 6.12.* | None listed |
| 6.18.34 | unaffected | semver | Unavailable | 6.18.* | None listed |
| 7.0.11 | unaffected | semver | Unavailable | 7.0.* | None listed |
| 7.1 | unaffected | original_commit_for_fix | Unavailable | * | None listed |