CVE-2026-64113ixgbevf: fix use-after-free in VEPA multicast source pruning
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: ixgbevf: fix use-after-free in VEPA multicast source pruning ixgbevf_clean_rx_irq() prunes frames whose source MAC matches the VF's own address (VEPA multicast workaround) by freeing the skb and continuing to the next descriptor: dev_kfree_skb_irq(skb); continue; The skb pointer is declared outside the while loop and persists across iterations. Because the continue skips the "skb = NULL" reset at the bottom of the loop, the next iteration enters the "else if (skb)" path and calls ixgbevf_add_rx_frag() on the freed skb, dereferencing skb_shinfo(skb)->nr_frags - a use-after-free in NAPI softirq context. The sibling driver iavf already handles this correctly by nulling the pointer before continuing. Apply the same pattern here. I do not have ixgbevf hardware; the bug was found by static analysis (scan_drop_continue_loops.py + semgrep drop_continue_in_loop, multi-tool corroboration with the highest score in the scan). The UAF was confirmed under KASAN by loading a test module that reproduces the exact code pattern (alloc skb, kfree_skb, then read skb_shinfo(skb)->nr_frags): BUG: KASAN: slab-use-after-free in ixgbevf_uaf_test_init+0x100/0x1000 Read of size 8 at addr 000000006163ae78 by task insmod/30 freed 208-byte region [000000006163adc0, 000000006163ae90) QEMU emulates igb (82576) but not ixgbe (82599), and the igbvf VF driver does not include the VEPA source pruning path, so a full end-to-end reproduction with emulated hardware was not possible.
- CVSS
- 9.8 CRITICAL (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Analyzed
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from bad17234ba702a50aeec50ab04724ee58af89607 before 3d931ac62411a7e43b85dba5fe45e1a4a91bd5cb; from bad17234ba702a50aeec50ab04724ee58af89607 before 6ef30384a50a50e4a484cddf341bc27de31aa3de; from bad17234ba702a50aeec50ab04724ee58af89607 before 55b3e91d62b2f7a24109b2d7c9f4c66d2e3b1ec1; from bad17234ba702a50aeec50ab04724ee58af89607 before add70e2682c0ad3be2a5810bcf1bc13963ba4df9; from bad17234ba702a50aeec50ab04724ee58af89607 before a244395d8c563ed1bb26c3ef708db6aeeaa08084; from bad17234ba702a50aeec50ab04724ee58af89607 before dfef79e09ed2f5df975c98547f97f5d7f8982a24; from bad17234ba702a50aeec50ab04724ee58af89607 before e8768bcbe5cd30c4ea36a22022c9ffaa66903693; from bad17234ba702a50aeec50ab04724ee58af89607 before 5d49b568c188dc77199d8d2b959c91da8cc27cf1 | CNA record |
linux linux_kernel linux:linux_kernel | from 3.19 before 5.10.258; from 5.11 before 5.15.209; from 5.16 before 6.1.175; from 6.2 before 6.6.142; from 6.7 before 6.12.92; from 6.13 before 6.18.34; from 6.19 before 7.0.11; 7.1; and 3 more ranges | NVD |
References
- https://git.kernel.org/stable/c/3d931ac62411a7e43b85dba5fe45e1a4a91bd5cbpatch
- https://git.kernel.org/stable/c/6ef30384a50a50e4a484cddf341bc27de31aa3depatch
- https://git.kernel.org/stable/c/55b3e91d62b2f7a24109b2d7c9f4c66d2e3b1ec1patch
- https://git.kernel.org/stable/c/add70e2682c0ad3be2a5810bcf1bc13963ba4df9patch
- https://git.kernel.org/stable/c/a244395d8c563ed1bb26c3ef708db6aeeaa08084patch
- https://git.kernel.org/stable/c/dfef79e09ed2f5df975c98547f97f5d7f8982a24patch
- https://git.kernel.org/stable/c/e8768bcbe5cd30c4ea36a22022c9ffaa66903693patch
- https://git.kernel.org/stable/c/5d49b568c188dc77199d8d2b959c91da8cc27cf1patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.