cbcvebase.
CVE-2026-64113
published 2026-07-19

CVE-2026-64113: 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…

PriorityP351critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
0.53%
43.0th percentile
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.

Affected

66 ranges· showing 25
VendorProductVersion rangeFixed in
linuxlinux——
linuxlinux>= bad17234ba702a50aeec50ab04724ee58af89607 < 3d931ac62411a7e43b85dba5fe45e1a4a91bd5cb3d931ac62411a7e43b85dba5fe45e1a4a91bd5cb
linuxlinux>= bad17234ba702a50aeec50ab04724ee58af89607 < 6ef30384a50a50e4a484cddf341bc27de31aa3de6ef30384a50a50e4a484cddf341bc27de31aa3de
linuxlinux>= bad17234ba702a50aeec50ab04724ee58af89607 < 55b3e91d62b2f7a24109b2d7c9f4c66d2e3b1ec155b3e91d62b2f7a24109b2d7c9f4c66d2e3b1ec1
linuxlinux>= bad17234ba702a50aeec50ab04724ee58af89607 < add70e2682c0ad3be2a5810bcf1bc13963ba4df9add70e2682c0ad3be2a5810bcf1bc13963ba4df9
linuxlinux>= bad17234ba702a50aeec50ab04724ee58af89607 < a244395d8c563ed1bb26c3ef708db6aeeaa08084a244395d8c563ed1bb26c3ef708db6aeeaa08084
linuxlinux>= bad17234ba702a50aeec50ab04724ee58af89607 < dfef79e09ed2f5df975c98547f97f5d7f8982a24dfef79e09ed2f5df975c98547f97f5d7f8982a24
linuxlinux>= bad17234ba702a50aeec50ab04724ee58af89607 < e8768bcbe5cd30c4ea36a22022c9ffaa66903693e8768bcbe5cd30c4ea36a22022c9ffaa66903693
linuxlinux>= bad17234ba702a50aeec50ab04724ee58af89607 < 5d49b568c188dc77199d8d2b959c91da8cc27cf15d49b568c188dc77199d8d2b959c91da8cc27cf1
linuxlinux_kernel——
linuxlinux_kernel——
linuxlinux_kernel——
linuxlinux_kernel——
linuxlinux_kernel——
linuxlinux_kernel>= 3.19 < 5.10.2585.10.258
linuxlinux_kernel>= 5.11 < 5.15.2095.15.209
linuxlinux_kernel>= 5.16 < 6.1.1756.1.175
linuxlinux_kernel>= 6.13 < 6.18.346.18.34
linuxlinux_kernel>= 6.19 < 7.0.117.0.11
linuxlinux_kernel>= 6.2 < 6.6.1426.6.142
linuxlinux_kernel>= 6.7 < 6.12.926.12.92
ubuntulinux——
ubuntulinux-aws——
ubuntulinux-aws-5.15——
ubuntulinux-aws-6.8——

CVSS provenance

nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vendor_redhat9.8CRITICAL
vendor_ubuntu9.1CRITICAL
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.