CVE-2024-26895

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-04-17. NVD baseline CVSS 7.8; sources differ by 0.0.

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

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

wifi: wilc1000: prevent use-after-free on vif when cleaning up all interfaces

wilc_netdev_cleanup currently triggers a KASAN warning, which can be observed on interface registration error path, or simply by removing the module/unbinding device from driver:

echo spi0.1 > /sys/bus/spi/drivers/wilc1000_spi/unbind

================================================================== BUG: KASAN: slab-use-after-free in wilc_netdev_cleanup+0x508/0x5cc Read of size 4 at addr c54d1ce8 by task sh/86

CPU: 0 PID: 86 Comm: sh Not tainted 6.8.0-rc1+ #117 Hardware name: Atmel SAMA5 unwind_backtrace from show_stack+0x18/0x1c show_stack from dump_stack_lvl+0x34/0x58 dump_stack_lvl from print_report+0x154/0x500 print_report from kasan_report+0xac/0xd8 kasan_report from wilc_netdev_cleanup+0x508/0x5cc wilc_netdev_cleanup from wilc_bus_remove+0xc8/0xec wilc_bus_remove from spi_remove+0x8c/0xac spi_remove from device_release_driver_internal+0x434/0x5f8 device_release_driver_internal from unbind_store+0xbc/0x108 unbind_store from kernfs_fop_write_iter+0x398/0x584 kernfs_fop_write_iter from vfs_write+0x728/0xf88 vfs_write from ksys_write+0x110/0x1e4 ksys_write from ret_fast_syscall+0x0/0x1c

[...]

Allocated by task 1: kasan_save_track+0x30/0x5c __kasan_kmalloc+0x8c/0x94 __kmalloc_node+0x1cc/0x3e4 kvmalloc_node+0x48/0x180 alloc_netdev_mqs+0x68/0x11dc alloc_etherdev_mqs+0x28/0x34 wilc_netdev_ifc_init+0x34/0x8ec wilc_cfg80211_init+0x690/0x910 wilc_bus_probe+0xe0/0x4a0 spi_probe+0x158/0x1b0 really_probe+0x270/0xdf4 __driver_probe_device+0x1dc/0x580 driver_probe_device+0x60/0x140 __driver_attach+0x228/0x5d4 bus_for_each_dev+0x13c/0x1a8 bus_add_driver+0x2a0/0x608 driver_register+0x24c/0x578 do_one_initcall+0x180/0x310 kernel_init_freeable+0x424/0x484 kernel_init+0x20/0x148 ret_from_fork+0x14/0x28

Freed by task 86: kasan_save_track+0x30/0x5c kasan_save_free_info+0x38/0x58 __kasan_slab_free+0xe4/0x140 kfree+0xb0/0x238 device_release+0xc0/0x2a8 kobject_put+0x1d4/0x46c netdev_run_todo+0x8fc/0x11d0 wilc_netdev_cleanup+0x1e4/0x5cc wilc_bus_remove+0xc8/0xec spi_remove+0x8c/0xac device_release_driver_internal+0x434/0x5f8 unbind_store+0xbc/0x108 kernfs_fop_write_iter+0x398/0x584 vfs_write+0x728/0xf88 ksys_write+0x110/0x1e4 ret_fast_syscall+0x0/0x1c [...]

David Mosberger-Tan initial investigation [1] showed that this use-after-free is due to netdevice unregistration during vif list traversal. When unregistering a net device, since the needs_free_netdev has been set to true during registration, the netdevice object is also freed, and as a consequence, the corresponding vif object too, since it is attached to it as private netdevice data. The next occurrence of the loop then tries to access freed vif pointer to the list to move forward in the list.

Fix this use-after-free thanks to two mechanisms:

  • navigate in the list with list_for_each_entry_safe, which allows to
safely modify the list as we go through each element. For each element, remove it from the list with list_del_rcu
  • make sure to wait for RCU grace period end after each vif removal to make
sure it is safe to free the corresponding vif too (through unregister_netdev)

Since we are in a RCU "modifier" path (not a "reader" path), and because such path is expected not to be concurrent to any other modifier (we are using the vif_mutex lock), we do not need to use RCU list API, that's why we can benefit from list_for_each_entry_safe.

[1] https://lore.kernel.org/linux-wireless/[email protected]/

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/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
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

April 17, 2024

Last Modified

August 5, 2026

Advisory Details (7)

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

wifi: wilc1000: prevent use-after-free on vif when cleaning up all interfaces - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5956f4203b6cdd0755bbdd21b45f3933c7026208
generic

wifi: wilc1000: prevent use-after-free on vif when cleaning up all interfaces - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3da9d32b7f4a1a9f7e4bb15bb82f2b2dd6719447
generic

wifi: wilc1000: prevent use-after-free on vif when cleaning up all interfaces - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/24228dcf1d30c2231caa332be7d3090ac59fbfe9
generic

wifi: wilc1000: prevent use-after-free on vif when cleaning up all interfaces - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: wilc1000: prevent use-after-free on vif when cleaning up all interfaces - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: wilc1000: prevent use-after-free on vif when cleaning up all interfaces - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: wilc1000: prevent use-after-free on vif when cleaning up all interfaces - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/73a2aa0aef86c2c07be5a2f42c9e6047e1a2f7bb

Patch Availability(16)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-intel-iotg-edge (5.15.0.1058.64~20.04.1) @ focal2026-05-22ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1063.63) @ jammy2026-05-22ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1066.64) @ jammy2026-05-22ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.113.123~20.04.1) @ focal2026-05-22ubuntu
ubuntulinux-tools-gke (6.8.0-1004.7) @ noble2026-05-22ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1006.6) @ noble2026-05-22ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1058.56) @ jammy2026-05-22ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1057.60~20.04.1) @ focal2026-05-22ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-35.35) @ noble2026-05-22ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1030.34) @ jammy2026-05-22ubuntu
ubuntulinux-tools-gcp (6.8.0-1008.9) @ noble2026-05-22ubuntu
ubuntulinux-tools-nvidia-lowlatency (5.15.0.1058.58) @ jammy2026-05-22ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1006.6+1) @ noble2026-05-22ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1061.57) @ jammy2026-05-22ubuntu
ubuntulinux-tools-kvm (5.15.0.1060.56) @ jammy2026-05-22ubuntu
linuxKernel @ 5.10.214—osv

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.

Weakness Classification(1)

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

All Vendor Advisories

(15)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 12× in last 7d / 44× 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 153 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2024-26895?
CVE-2024-26895 is a high vulnerability published on April 17, 2024. In the Linux kernel, the following vulnerability has been resolved: wifi: wilc1000: prevent use-after-free on vif when cleaning up all interfaces wilcnetdevcleanup currently triggers a KASAN warning, which can be observed on interface registration error path, or simply by removing the…
When was CVE-2024-26895 disclosed?
CVE-2024-26895 was first published in the National Vulnerability Database on April 17, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-26895 actively exploited?
CVE-2024-26895 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.6% of all scored CVEs.
What is the CVSS score of CVE-2024-26895?
CVE-2024-26895 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-26895?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-26895, 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

Explore the affected products and dependency analysis for CVE-2024-26895

Explore →

Is Your Infrastructure Affected by CVE-2024-26895?

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

Start Free Scan →Browse All CVEs