CVE-2024-39502

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-07-12. 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-38028 (ENISA EUVD) · GHSA-28h9-44vg-f29v (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.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ionic: fix use after netif_napi_del()

When queues are started, netif_napi_add() and napi_enable() are called. If there are 4 queues and only 3 queues are used for the current configuration, only 3 queues' napi should be registered and enabled. The ionic_qcq_enable() checks whether the .poll pointer is not NULL for enabling only the using queue' napi. Unused queues' napi will not be registered by netif_napi_add(), so the .poll pointer indicates NULL. But it couldn't distinguish whether the napi was unregistered or not because netif_napi_del() doesn't reset the .poll pointer to NULL. So, ionic_qcq_enable() calls napi_enable() for the queue, which was unregistered by netif_napi_del().

Reproducer: ethtool -L rx 1 tx 1 combined 0 ethtool -L rx 0 tx 0 combined 1 ethtool -L rx 0 tx 0 combined 4

Splat looks like: kernel BUG at net/core/dev.c:6666! Oops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI CPU: 3 PID: 1057 Comm: kworker/3:3 Not tainted 6.10.0-rc2+ #16 Workqueue: events ionic_lif_deferred_work [ionic] RIP: 0010:napi_enable+0x3b/0x40 Code: 48 89 c2 48 83 e2 f6 80 b9 61 09 00 00 00 74 0d 48 83 bf 60 01 00 00 00 74 03 80 ce 01 f0 4f RSP: 0018:ffffb6ed83227d48 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff97560cda0828 RCX: 0000000000000029 RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff97560cda0a28 RBP: ffffb6ed83227d50 R08: 0000000000000400 R09: 0000000000000001 R10: 0000000000000001 R11: 0000000000000001 R12: 0000000000000000 R13: ffff97560ce3c1a0 R14: 0000000000000000 R15: ffff975613ba0a20 FS: 0000000000000000(0000) GS:ffff975d5f780000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f8f734ee200 CR3: 0000000103e50000 CR4: 00000000007506f0 PKRU: 55555554 Call Trace: ? die+0x33/0x90 ? do_trap+0xd9/0x100 ? napi_enable+0x3b/0x40 ? do_error_trap+0x83/0xb0 ? napi_enable+0x3b/0x40 ? napi_enable+0x3b/0x40 ? exc_invalid_op+0x4e/0x70 ? napi_enable+0x3b/0x40 ? asm_exc_invalid_op+0x16/0x20 ? napi_enable+0x3b/0x40 ionic_qcq_enable+0xb7/0x180 [ionic 59bdfc8a035436e1c4224ff7d10789e3f14643f8] ionic_start_queues+0xc4/0x290 [ionic 59bdfc8a035436e1c4224ff7d10789e3f14643f8] ionic_link_status_check+0x11c/0x170 [ionic 59bdfc8a035436e1c4224ff7d10789e3f14643f8] ionic_lif_deferred_work+0x129/0x280 [ionic 59bdfc8a035436e1c4224ff7d10789e3f14643f8] process_one_work+0x145/0x360 worker_thread+0x2bb/0x3d0 ? __pfx_worker_thread+0x10/0x10 kthread+0xcc/0x100 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x2d/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30

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.3% × 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.3%
EPSS %ILE
23rd
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.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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

July 12, 2024

Last Modified

October 15, 2026

Advisory Details (7)

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

ionic: fix use after netif_napi_del() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/60cd714871cd5a683353a355cbb17a685245cf84
Web page

ionic: fix use after netif_napi_del() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/183ebc167a8a19e916b885d4bb61a3491991bfa5
Web page

ionic: fix use after netif_napi_del() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0d19267cb150e8f76ade210e16ee820a77f684e7
Web page

ionic: fix use after netif_napi_del() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ff9c2a9426ecf5b9631e9fd74993b357262387d6
Web page

ionic: fix use after netif_napi_del() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a87d72b37b9ec2c1e18fe36b09241d8b30334a2e
Web page

ionic: fix use after netif_napi_del() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8edd18dab443863e9e48f084e7f123fca3065e4e
Web page

ionic: fix use after netif_napi_del() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/79f18a41dd056115d685f3b0a419c7cd40055e13

Vendor Advisories for CVE-2024-39502(11)

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

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1013.14.1) @ noble2026-10-29ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.121.121) @ jammy2026-10-29ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.121.110) @ jammy2026-10-29ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.195.193) @ focal2026-10-29ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.195.215~18.04.1) @ bionic2026-10-29ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-44.44) @ noble2026-10-29ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1051 (5.4.0-1051.55) @ focal2026-10-29ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1013.14~22.04.1) @ jammy2026-10-29ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-44.44.1~22.04.1) @ jammy2026-10-29ubuntu
ubuntulinux-tools-azure (6.8.0-1014.16) @ noble2026-10-29ubuntu
ubuntulinux-tools-iot (5.4.0.1043.41) @ focal2026-10-29ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1035.39) @ jammy2026-10-29ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1072.70) @ jammy2026-10-29ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1067.73~20.04.1) @ focal2026-10-29ubuntu
ubuntulinux-tools-raspi (6.8.0-1011.12) @ noble2026-10-29ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-45.45~22.04.1) @ jammy2026-10-29ubuntu
ubuntulinux-tools-azure-fde-edge (5.15.0.1072.81~20.04.1.49) @ focal2026-10-29ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1116.146) @ focal2026-10-29ubuntu
ubuntulinux-tools-raspi-hwe-18.04-edge (5.4.0.1116.128~18.04.1) @ bionic2026-10-29ubuntu
redhatkernel-0:5.14.0-427.40.1.el9_42024-10-16redhat
redhatkernel-rt-0:5.14.0-284.82.1.rt14.367.el9_22024-09-04redhat
redhatkernel-0:5.14.0-284.82.1.el9_22024-09-04redhat
redhatkernel-0:4.18.0-477.70.1.el8_82024-09-03redhat
redhatkernel-0:4.18.0-372.118.1.el8_62024-08-13redhat
redhatkernel-0:5.14.0-70.112.1.el9_02024-08-13redhat
redhatkernel-rt-0:4.18.0-305.138.1.rt7.214.el8_42024-08-13redhat
redhatkernel-0:4.18.0-305.138.1.el8_42024-08-13redhat
redhatkernel-rt-0:5.14.0-70.112.1.rt21.184.el9_02024-08-13redhat
redhatkernel-0:4.18.0-553.16.1.el8_102024-08-08redhat
redhatkernel-rt-0:4.18.0-553.16.1.rt7.357.el8_102024-08-08redhat
linuxKernel @ 5.4.279 (fixes >=5.4.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 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (41 versions)
  • every version up to 5.10.221-1: fixed in 5.10.221-1
—
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1
  • every version up to 6.1.119-1~deb11u1: fixed in 6.1.119-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.98-1 (25 versions)
  • every version up to 6.1.99-1: fixed in 6.1.99-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.9.7-1: fixed in 6.9.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.9.7-1: fixed in 6.9.7-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(14)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 46× 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 96 of 244 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 148 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-39502?
CVE-2024-39502 is a high-severity vulnerability; its CVE record was published on July 12, 2024. In the Linux kernel, the following vulnerability has been resolved: ionic: fix use after netif_napi_del() When queues are started, netif_napi_add() and napi_enable() are called. If there are 4 queues and only 3 queues are used for the current configuration, only 3 queues' napi should be registered…
When was the CVE record for CVE-2024-39502 published?
The CVE record for CVE-2024-39502 was published on July 12, 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-39502 actively exploited?
CVE-2024-39502 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-39502?
CVE-2024-39502 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-39502?
A fix for CVE-2024-39502 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-39502 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-39502

Explore →

Is Your Infrastructure Affected by CVE-2024-39502?

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

Book a Demo →Browse All CVEs