CVE-2024-26895

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2024-24157 (ENISA EUVD) · GHSA-6r45-w96c-v9jx (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

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/ab077dbe58b1ea5de0a3b2ca21f275a07af967d2.camel@egauge.net/

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
14th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 17, 2024

Last Modified

October 15, 2026

Advisory Details (7)

Auto-updated Aug 4, 2026
Patch available.
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-35.35) @ noble2026-10-29ubuntu
ubuntulinux-tools-gcp (6.8.0-1008.9) @ noble2026-10-29ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1063.63) @ jammy2026-10-29ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1030.34) @ jammy2026-10-29ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1058.64~20.04.1) @ focal2026-10-29ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1061.57) @ jammy2026-10-29ubuntu
ubuntulinux-tools-kvm (5.15.0.1060.56) @ jammy2026-10-29ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1006.6+1) @ noble2026-10-29ubuntu
ubuntulinux-tools-nvidia-lowlatency (5.15.0.1058.58) @ jammy2026-10-29ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1066.64) @ jammy2026-10-29ubuntu
ubuntulinux-tools-gke (6.8.0-1004.7) @ noble2026-10-29ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.113.123~20.04.1) @ focal2026-10-29ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1006.6) @ noble2026-10-29ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1057.60~20.04.1) @ focal2026-10-29ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1058.56) @ jammy2026-10-29ubuntu
linuxKernel @ 5.10.214 (fixes >=5.5.0)—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.

Affected Packages

(5 across 5 ecosystems)
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
linux-5.105.10.136-1~deb10u1 ... 5.10.209-2~deb10u1 (13 versions)
  • every version up to 5.10.216-1~deb10u1: fixed in 5.10.216-1~deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (39 versions)
  • every version up to 5.10.216-1: fixed in 5.10.216-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.82-1 (19 versions)
  • every version up to 6.1.85-1: fixed in 6.1.85-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.12-1: fixed in 6.7.12-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.12-1: fixed in 6.7.12-1
—

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 10× in last 7d / 45× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 242 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 144 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-26895?
CVE-2024-26895 is a high-severity vulnerability; its CVE record was 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 wilc_netdev_cleanup currently triggers a KASAN warning, which can be observed on interface registration error path, or simply by removing the…
When was the CVE record for CVE-2024-26895 published?
The CVE record for CVE-2024-26895 was published on April 17, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
Is CVE-2024-26895 actively exploited?
CVE-2024-26895 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-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?
A fix for CVE-2024-26895 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs