CVE-2026-64113

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-19. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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 v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 12, 2026

Advisory Details (8)

Auto-updated Aug 26, 2026
No patch confirmed yet.
generic

ixgbevf: fix use-after-free in VEPA multicast source pruning - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e8768bcbe5cd30c4ea36a22022c9ffaa66903693
generic

ixgbevf: fix use-after-free in VEPA multicast source pruning - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dfef79e09ed2f5df975c98547f97f5d7f8982a24
generic

ixgbevf: fix use-after-free in VEPA multicast source pruning - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/add70e2682c0ad3be2a5810bcf1bc13963ba4df9
generic

ixgbevf: fix use-after-free in VEPA multicast source pruning - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a244395d8c563ed1bb26c3ef708db6aeeaa08084
generic

ixgbevf: fix use-after-free in VEPA multicast source pruning - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6ef30384a50a50e4a484cddf341bc27de31aa3de
generic

ixgbevf: fix use-after-free in VEPA multicast source pruning - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5d49b568c188dc77199d8d2b959c91da8cc27cf1
generic

ixgbevf: fix use-after-free in VEPA multicast source pruning - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/55b3e91d62b2f7a24109b2d7c9f4c66d2e3b1ec1
generic

ixgbevf: fix use-after-free in VEPA multicast source pruning - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3d931ac62411a7e43b85dba5fe45e1a4a91bd5cb

Vendor Advisories for CVE-2026-64113(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(16)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(16)

Data Freshness Timeline

(refreshed 58× in last 7d / 349× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 439 total refreshes for this CVE.

  1. 2026-08-30 07:15 UTCVendor advisory
  2. 2026-08-30 07:15 UTCGHSA enrichment
  3. 2026-08-30 02:46 UTCEG score recompute
  4. 2026-08-30 02:46 UTCVendor advisory
  5. 2026-08-30 02:46 UTCGHSA enrichment
  6. 2026-08-30 01:22 UTCEPSS rescore
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-28 01:42 UTCVendor advisory
  9. 2026-08-28 01:41 UTCGHSA enrichment
  10. 2026-08-27 21:22 UTCEG score recompute
  11. 2026-08-27 21:22 UTCVendor advisory
  12. 2026-08-27 21:22 UTCGHSA enrichment
  13. 2026-08-27 11:48 UTCVendor advisory
  14. 2026-08-27 11:48 UTCGHSA enrichment
  15. 2026-08-27 02:36 UTCVendor advisory
  16. 2026-08-27 02:36 UTCGHSA enrichment
  17. 2026-08-26 22:15 UTCEG score recompute
  18. 2026-08-26 22:15 UTCVendor advisory
  19. 2026-08-26 22:15 UTCGHSA enrichment
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-26 13:42 UTCVendor advisory
  22. 2026-08-26 13:41 UTCGHSA enrichment
  23. 2026-08-26 08:57 UTCVendor advisory
  24. 2026-08-26 08:57 UTCGHSA enrichment
  25. 2026-08-26 04:31 UTCVendor advisory
Show 75 more
  1. 2026-08-26 04:30 UTCGHSA enrichment
  2. 2026-08-25 23:44 UTCVendor advisory
  3. 2026-08-25 23:44 UTCGHSA enrichment
  4. 2026-08-25 18:47 UTCEG score recompute
  5. 2026-08-25 18:47 UTCVendor advisory
  6. 2026-08-25 18:46 UTCGHSA enrichment
  7. 2026-08-25 13:49 UTCEPSS rescore
  8. 2026-08-25 12:16 UTCVendor advisory
  9. 2026-08-25 12:16 UTCGHSA enrichment
  10. 2026-08-25 07:55 UTCVendor advisory
  11. 2026-08-25 07:55 UTCGHSA enrichment
  12. 2026-08-25 03:36 UTCVendor advisory
  13. 2026-08-25 03:36 UTCGHSA enrichment
  14. 2026-08-24 23:19 UTCVendor advisory
  15. 2026-08-24 23:19 UTCGHSA enrichment
  16. 2026-08-24 19:02 UTCEG score recompute
  17. 2026-08-24 19:02 UTCVendor advisory
  18. 2026-08-24 19:02 UTCGHSA enrichment
  19. 2026-08-24 12:19 UTCEG score recompute
  20. 2026-08-24 12:19 UTCVendor advisory
  21. 2026-08-24 12:19 UTCGHSA enrichment
  22. 2026-08-24 08:02 UTCVendor advisory
  23. 2026-08-24 08:02 UTCGHSA enrichment
  24. 2026-08-24 03:43 UTCVendor advisory
  25. 2026-08-24 03:43 UTCGHSA enrichment
  26. 2026-08-23 23:03 UTCVendor advisory
  27. 2026-08-23 23:03 UTCGHSA enrichment
  28. 2026-08-23 18:27 UTCVendor advisory
  29. 2026-08-23 18:27 UTCGHSA enrichment
  30. 2026-08-23 14:09 UTCVendor advisory
  31. 2026-08-23 14:09 UTCGHSA enrichment
  32. 2026-08-23 09:52 UTCVendor advisory
  33. 2026-08-23 09:52 UTCGHSA enrichment
  34. 2026-08-23 05:35 UTCVendor advisory
  35. 2026-08-23 05:34 UTCGHSA enrichment
  36. 2026-08-23 01:17 UTCEG score recompute
  37. 2026-08-23 01:17 UTCVendor advisory
  38. 2026-08-23 01:17 UTCGHSA enrichment
  39. 2026-08-23 00:19 UTCEPSS rescore
  40. 2026-08-22 20:59 UTCVendor advisory
  41. 2026-08-22 20:59 UTCGHSA enrichment
  42. 2026-08-22 16:41 UTCVendor advisory
  43. 2026-08-22 16:41 UTCGHSA enrichment
  44. 2026-08-22 12:08 UTCVendor advisory
  45. 2026-08-22 12:08 UTCGHSA enrichment
  46. 2026-08-22 07:29 UTCVendor advisory
  47. 2026-08-22 07:29 UTCGHSA enrichment
  48. 2026-08-22 03:12 UTCEG score recompute
  49. 2026-08-22 03:12 UTCVendor advisory
  50. 2026-08-22 03:12 UTCGHSA enrichment
  51. 2026-08-21 23:49 UTCEPSS rescore
  52. 2026-08-21 22:53 UTCVendor advisory
  53. 2026-08-21 22:53 UTCGHSA enrichment
  54. 2026-08-21 18:36 UTCVendor advisory
  55. 2026-08-21 18:36 UTCGHSA enrichment
  56. 2026-08-21 14:18 UTCVendor advisory
  57. 2026-08-21 14:18 UTCGHSA enrichment
  58. 2026-08-21 10:01 UTCVendor advisory
  59. 2026-08-21 10:01 UTCGHSA enrichment
  60. 2026-08-21 05:44 UTCVendor advisory
  61. 2026-08-21 05:44 UTCGHSA enrichment
  62. 2026-08-21 01:27 UTCEG score recompute
  63. 2026-08-21 01:27 UTCVendor advisory
  64. 2026-08-21 01:26 UTCGHSA enrichment
  65. 2026-08-20 22:55 UTCEPSS rescore
  66. 2026-08-20 21:09 UTCVendor advisory
  67. 2026-08-20 21:09 UTCGHSA enrichment
  68. 2026-08-20 16:51 UTCVendor advisory
  69. 2026-08-20 16:51 UTCGHSA enrichment
  70. 2026-08-20 12:14 UTCVendor advisory
  71. 2026-08-20 12:14 UTCGHSA enrichment
  72. 2026-08-20 07:52 UTCVendor advisory
  73. 2026-08-20 07:52 UTCGHSA enrichment
  74. 2026-08-20 03:35 UTCVendor advisory
  75. 2026-08-20 03:35 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-64113?
CVE-2026-64113 is a critical vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: ixgbevf: fix use-after-free in VEPA multicast source pruning ixgbevfcleanrx_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:…
When was CVE-2026-64113 disclosed?
CVE-2026-64113 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64113 actively exploited?
CVE-2026-64113 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.5% of all scored CVEs.
What is the CVSS score of CVE-2026-64113?
CVE-2026-64113 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-64113?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64113, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64113

Explore →

Is Your Infrastructure Affected by CVE-2026-64113?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.