ixgbevf: fix use-after-free in VEPA multicast source pruning
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.258, 5.15.209, 6.1.175, 6.6.142, 6.12.92, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From bad17234ba702a50aeec50ab04724ee58af89607 · fixed in 3d931ac62411a7e43b85dba5fe45e1a4a91bd5cb; From bad17234ba702a50aeec50ab04724ee58af89607 · fixed in 6ef30384a50a50e4a484cddf341bc27de31aa3de; From bad17234ba702a50aeec50ab04724ee58af89607 · fixed in 55b3e91d62b2f7a24109b2d7c9f4c66d2e3b1ec1; From bad17234ba702a50aeec50ab04724ee58af89607 · fixed in add70e2682c0ad3be2a5810bcf1bc13963ba4df9; From bad17234ba702a50aeec50ab04724ee58af89607 · fixed in a244395d8c563ed1bb26c3ef708db6aeeaa08084; From bad17234ba702a50aeec50ab04724ee58af89607 · fixed in dfef79e09ed2f5df975c98547f97f5d7f8982a24; From bad17234ba702a50aeec50ab04724ee58af89607 · fixed in e8768bcbe5cd30c4ea36a22022c9ffaa66903693; From bad17234ba702a50aeec50ab04724ee58af89607 · fixed in 5d49b568c188dc77199d8d2b959c91da8cc27cf1
- Linux Linux
3.19
- KernelLinux
From 3.19.0 · fixed in 5.10.258; From 5.11.0 · fixed in 5.15.209; From 5.16.0 · fixed in 6.1.175; From 6.2.0 · fixed in 6.6.142; From 6.7.0 · fixed in 6.12.92; From 6.13.0 · fixed in 6.18.34; From 6.19.0 · fixed in 7.0.11
References 8
git.kernel.org
- stable/c/3d931ac62411a7e43b85dba5fe45e1a4a91bd5cb
- stable/c/6ef30384a50a50e4a484cddf341bc27de31aa3de
- stable/c/55b3e91d62b2f7a24109b2d7c9f4c66d2e3b1ec1
- stable/c/add70e2682c0ad3be2a5810bcf1bc13963ba4df9
- stable/c/a244395d8c563ed1bb26c3ef708db6aeeaa08084
- stable/c/dfef79e09ed2f5df975c98547f97f5d7f8982a24
- stable/c/e8768bcbe5cd30c4ea36a22022c9ffaa66903693
- stable/c/5d49b568c188dc77199d8d2b959c91da8cc27cf1