CVE-2024-38595

MEDIUMCVSS · not yet scored5.5
EchelonGraph scoreLOW confidence

Score 5.5 from GitHub Security Advisory published 2024-06-19.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

A fix is available — apply it.

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

net/mlx5: Fix peer devlink set for SF representor devlink port

The cited patch change register devlink flow, and neglect to reflect the changes for peer devlink set logic. Peer devlink set is triggering a call trace if done after devl_register.[1]

Hence, align peer devlink set logic with register devlink flow.

[1] WARNING: CPU: 4 PID: 3394 at net/devlink/core.c:155 devlink_rel_nested_in_add+0x177/0x180 CPU: 4 PID: 3394 Comm: kworker/u40:1 Not tainted 6.9.0-rc4_for_linust_min_debug_2024_04_16_14_08 #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 Workqueue: mlx5_vhca_event0 mlx5_vhca_state_work_handler [mlx5_core] RIP: 0010:devlink_rel_nested_in_add+0x177/0x180 Call Trace: ? __warn+0x78/0x120 ? devlink_rel_nested_in_add+0x177/0x180 ? report_bug+0x16d/0x180 ? handle_bug+0x3c/0x60 ? exc_invalid_op+0x14/0x70 ? asm_exc_invalid_op+0x16/0x20 ? devlink_port_init+0x30/0x30 ? devlink_port_type_clear+0x50/0x50 ? devlink_rel_nested_in_add+0x177/0x180 ? devlink_rel_nested_in_add+0xdd/0x180 mlx5_sf_mdev_event+0x74/0xb0 [mlx5_core] notifier_call_chain+0x35/0xb0 blocking_notifier_call_chain+0x3d/0x60 mlx5_blocking_notifier_call_chain+0x22/0x30 [mlx5_core] mlx5_sf_dev_probe+0x185/0x3e0 [mlx5_core] auxiliary_bus_probe+0x38/0x80 ? driver_sysfs_add+0x51/0x80 really_probe+0xc5/0x3a0 ? 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+0x64f/0x860 __auxiliary_device_add+0x3b/0xa0 mlx5_sf_dev_add+0x139/0x330 [mlx5_core] mlx5_sf_dev_state_change_handler+0x1e4/0x250 [mlx5_core] notifier_call_chain+0x35/0xb0 blocking_notifier_call_chain+0x3d/0x60 mlx5_vhca_state_work_handler+0x151/0x200 [mlx5_core] process_one_work+0x13f/0x2e0 worker_thread+0x2bd/0x3c0 ? rescuer_thread+0x410/0x410 kthread+0xc4/0xf0 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x2d/0x50 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork_asm+0x11/0x20

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

Published

June 19, 2024

Last Modified

May 27, 2026

References (3)

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-40.40) @ noble2026-05-23ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1010.10) @ noble2026-05-23ubuntu
ubuntulinux-tools-raspi (6.8.0-1009.10) @ noble2026-05-23ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1010.10) @ noble2026-05-23ubuntu
linuxKernel @ 6.8.12—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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.8.12-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.8.12-1—

All Vendor Advisories

(4)

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 8× in last 7d / 32× 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 165 total refreshes for this CVE.

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

Related CVEs(same product + same vendor)

Frequently asked(4)

What is CVE-2024-38595?
CVE-2024-38595 is a medium vulnerability published on June 19, 2024. In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Fix peer devlink set for SF representor devlink port The cited patch change register devlink flow, and neglect to reflect the changes for peer devlink set logic. Peer devlink set is triggering a call trace if done after…
When was CVE-2024-38595 disclosed?
CVE-2024-38595 was first published in the National Vulnerability Database on June 19, 2024, with the most recent update on May 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-38595 actively exploited?
CVE-2024-38595 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 88.6% of all scored CVEs.
How do I remediate CVE-2024-38595?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-38595, 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-2024-38595

Explore →

Is Your Infrastructure Affected by CVE-2024-38595?

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

Start Free Scan →Browse All CVEs