CVE-2024-38608

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2024-06-19. NVD baseline CVSS 5.5; 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
5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

net/mlx5e: Fix netif state handling

mlx5e_suspend cleans resources only if netif_device_present() returns true. However, mlx5e_resume changes the state of netif, via mlx5e_nic_enable, only if reg_state == NETREG_REGISTERED. In the below case, the above leads to NULL-ptr Oops[1] and memory leaks:

mlx5e_probe _mlx5e_resume mlx5e_attach_netdev mlx5e_nic_enable <-- netdev not reg, not calling netif_device_attach() register_netdev <-- failed for some reason. ERROR_FLOW: _mlx5e_suspend <-- netif_device_present return false, resources aren't freed :(

Hence, clean resources in this case as well.

[1] BUG: kernel NULL pointer dereference, address: 0000000000000000 PGD 0 P4D 0 Oops: 0010 [#1] SMP CPU: 2 PID: 9345 Comm: test-ovs-ct-gen Not tainted 6.5.0_for_upstream_min_debug_2023_09_05_16_01 #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:0x0 Code: Unable to access opcode bytes at0xffffffffffffffd6. RSP: 0018:ffff888178aaf758 EFLAGS: 00010246 Call Trace: ? __die+0x20/0x60 ? page_fault_oops+0x14c/0x3c0 ? exc_page_fault+0x75/0x140 ? asm_exc_page_fault+0x22/0x30 notifier_call_chain+0x35/0xb0 blocking_notifier_call_chain+0x3d/0x60 mlx5_blocking_notifier_call_chain+0x22/0x30 [mlx5_core] mlx5_core_uplink_netdev_event_replay+0x3e/0x60 [mlx5_core] mlx5_mdev_netdev_track+0x53/0x60 [mlx5_ib] mlx5_ib_roce_init+0xc3/0x340 [mlx5_ib] __mlx5_ib_add+0x34/0xd0 [mlx5_ib] mlx5r_probe+0xe1/0x210 [mlx5_ib] ? auxiliary_match_id+0x6a/0x90 auxiliary_bus_probe+0x38/0x80 ? driver_sysfs_add+0x51/0x80 really_probe+0xc9/0x3e0 ? driver_probe_device+0x90/0x90 __driver_probe_device+0x80/0x160 driver_probe_device+0x1e/0x90 __device_attach_driver+0x7d/0x100 bus_for_each_drv+0x80/0xd0 __device_attach+0xbc/0x1f0 bus_probe_device+0x86/0xa0 device_add+0x637/0x840 __auxiliary_device_add+0x3b/0xa0 add_adev+0xc9/0x140 [mlx5_core] mlx5_rescan_drivers_locked+0x22a/0x310 [mlx5_core] mlx5_register_device+0x53/0xa0 [mlx5_core] mlx5_init_one_devl_locked+0x5c4/0x9c0 [mlx5_core] mlx5_init_one+0x3b/0x60 [mlx5_core] probe_one+0x44c/0x730 [mlx5_core] local_pci_probe+0x3e/0x90 pci_device_probe+0xbf/0x210 ? kernfs_create_link+0x5d/0xa0 ? sysfs_do_create_link_sd+0x60/0xc0 really_probe+0xc9/0x3e0 ? driver_probe_device+0x90/0x90 __driver_probe_device+0x80/0x160 driver_probe_device+0x1e/0x90 __device_attach_driver+0x7d/0x100 bus_for_each_drv+0x80/0xd0 __device_attach+0xbc/0x1f0 pci_bus_add_device+0x54/0x80 pci_iov_add_virtfn+0x2e6/0x320 sriov_enable+0x208/0x420 mlx5_core_sriov_configure+0x9e/0x200 [mlx5_core] sriov_numvfs_store+0xae/0x1a0 kernfs_fop_write_iter+0x10c/0x1a0 vfs_write+0x291/0x3c0 ksys_write+0x5f/0xe0 do_syscall_64+0x3d/0x90 entry_SYSCALL_64_after_hwframe+0x46/0xb0 CR2: 0000000000000000 ---[ end trace 0000000000000000 ]---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 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
11th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-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. 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: 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.

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

June 19, 2024

Last Modified

October 21, 2026

References (3)

Vendor Advisories for CVE-2024-38608(7)

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

Patch Availability(17)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-60.63~22.04.1) @ jammy2026-10-21ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1026.27~22.04.1) @ jammy2026-10-21ubuntu
ubuntulinux-tools-realtime (6.8.1-1022.23) @ noble2026-10-21ubuntu
ubuntulinux-tools-gke (6.8.0-1025.29) @ noble2026-10-21ubuntu
ubuntulinux-tools-raspi-realtime (6.8.0-2023.24) @ noble2026-10-21ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1028.31.1) @ noble2026-10-21ubuntu
ubuntulinux-tools-raspi (6.8.0-1028.32) @ noble2026-10-21ubuntu
ubuntulinux-virtual (6.8.0-60.63) @ noble2026-10-21ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1028.28) @ noble2026-10-21ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1016.17) @ noble2026-10-21ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1012.14) @ noble2026-10-21ubuntu
redhatkernel-0:4.18.0-553.27.1.el8_102024-11-05redhat
redhatkernel-rt-0:4.18.0-553.27.1.rt7.368.el8_102024-11-05redhat
redhatkernel-0:5.14.0-427.33.1.el9_42024-08-28redhat
redhatkernel-rt-0:5.14.0-284.80.1.rt14.365.el9_22024-08-21redhat
redhatkernel-0:5.14.0-284.80.1.el9_22024-08-21redhat
linuxKernel @ 6.9.3 (fixes >=4.12.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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (353 versions)
  • every version on: no fix on record
—
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

(11)

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 15× in last 7d / 42× 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 94 of 204 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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 110 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-38608?
CVE-2024-38608 is a medium-severity vulnerability; its CVE record was published on June 19, 2024. In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix netif state handling mlx5esuspend cleans resources only if netifdevice_present() returns true. However, mlx5e_resume changes the state of netif, via mlx5enicenable, only if regstate == NETREGREGISTERED. In the below…
When was the CVE record for CVE-2024-38608 published?
The CVE record for CVE-2024-38608 was published on June 19, 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 21, 2026; the record at its source may have been updated since.
Is CVE-2024-38608 actively exploited?
CVE-2024-38608 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-38608?
CVE-2024-38608 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-38608?
A fix for CVE-2024-38608 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-38608 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-38608

Explore →

Is Your Infrastructure Affected by CVE-2024-38608?

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

Book a Demo →Browse All CVEs