CVE-2024-36004

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2024-05-20. NVD baseline CVSS 5.5; sources differ by 0.0.

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

A fix is available — apply it.

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

i40e: Do not use WQ_MEM_RECLAIM flag for workqueue

Issue reported by customer during SRIOV testing, call trace: When both i40e and the i40iw driver are loaded, a warning in check_flush_dependency is being triggered. This seems to be because of the i40e driver workqueue is allocated with the WQ_MEM_RECLAIM flag, and the i40iw one is not.

Similar error was encountered on ice too and it was fixed by removing the flag. Do the same for i40e too.

[Feb 9 09:08] ------------[ cut here ]------------ [ +0.000004] workqueue: WQ_MEM_RECLAIM i40e:i40e_service_task [i40e] is flushing !WQ_MEM_RECLAIM infiniband:0x0 [ +0.000060] WARNING: CPU: 0 PID: 937 at kernel/workqueue.c:2966 check_flush_dependency+0x10b/0x120 [ +0.000007] Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_timer snd_seq_device snd soundcore nls_utf8 cifs cifs_arc4 nls_ucs2_utils rdma_cm iw_cm ib_cm cifs_md4 dns_resolver netfs qrtr rfkill sunrpc vfat fat intel_rapl_msr intel_rapl_common irdma intel_uncore_frequency intel_uncore_frequency_common ice ipmi_ssif isst_if_common skx_edac nfit libnvdimm x86_pkg_temp_thermal intel_powerclamp gnss coretemp ib_uverbs rapl intel_cstate ib_core iTCO_wdt iTCO_vendor_support acpi_ipmi mei_me ipmi_si intel_uncore ioatdma i2c_i801 joydev pcspkr mei ipmi_devintf lpc_ich intel_pch_thermal i2c_smbus ipmi_msghandler acpi_power_meter acpi_pad xfs libcrc32c ast sd_mod drm_shmem_helper t10_pi drm_kms_helper sg ixgbe drm i40e ahci crct10dif_pclmul libahci crc32_pclmul igb crc32c_intel libata ghash_clmulni_intel i2c_algo_bit mdio dca wmi dm_mirror dm_region_hash dm_log dm_mod fuse [ +0.000050] CPU: 0 PID: 937 Comm: kworker/0:3 Kdump: loaded Not tainted 6.8.0-rc2-Feb-net_dev-Qiueue-00279-gbd43c5687e05 #1 [ +0.000003] Hardware name: Intel Corporation S2600BPB/S2600BPB, BIOS SE5C620.86B.02.01.0013.121520200651 12/15/2020 [ +0.000001] Workqueue: i40e i40e_service_task [i40e] [ +0.000024] RIP: 0010:check_flush_dependency+0x10b/0x120 [ +0.000003] Code: ff 49 8b 54 24 18 48 8d 8b b0 00 00 00 49 89 e8 48 81 c6 b0 00 00 00 48 c7 c7 b0 97 fa 9f c6 05 8a cc 1f 02 01 e8 35 b3 fd ff <0f> 0b e9 10 ff ff ff 80 3d 78 cc 1f 02 00 75 94 e9 46 ff ff ff 90 [ +0.000002] RSP: 0018:ffffbd294976bcf8 EFLAGS: 00010282 [ +0.000002] RAX: 0000000000000000 RBX: ffff94d4c483c000 RCX: 0000000000000027 [ +0.000001] RDX: ffff94d47f620bc8 RSI: 0000000000000001 RDI: ffff94d47f620bc0 [ +0.000001] RBP: 0000000000000000 R08: 0000000000000000 R09: 00000000ffff7fff [ +0.000001] R10: ffffbd294976bb98 R11: ffffffffa0be65e8 R12: ffff94c5451ea180 [ +0.000001] R13: ffff94c5ab5e8000 R14: ffff94c5c20b6e05 R15: ffff94c5f1330ab0 [ +0.000001] FS: 0000000000000000(0000) GS:ffff94d47f600000(0000) knlGS:0000000000000000 [ +0.000002] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ +0.000001] CR2: 00007f9e6f1fca70 CR3: 0000000038e20004 CR4: 00000000007706f0 [ +0.000000] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ +0.000001] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ +0.000001] PKRU: 55555554 [ +0.000001] Call Trace: [ +0.000001] [ +0.000002] ? __warn+0x80/0x130 [ +0.000003] ? check_flush_dependency+0x10b/0x120 [ +0.000002] ? report_bug+0x195/0x1a0 [ +0.000005] ? handle_bug+0x3c/0x70 [ +0.000003] ? exc_invalid_op+0x14/0x70 [ +0.000002] ? asm_exc_invalid_op+0x16/0x20 [ +0.000006] ? check_flush_dependency+0x10b/0x120 [ +0.000002] ? check_flush_dependency+0x10b/0x120 [ +0.000002] __flush_workqueue+0x126/0x3f0 [ +0.000015] ib_cache_cleanup_one+0x1c/0xe0 [ib_core] [ +0.000056] __ib_unregister_device+0x6a/0xb0 [ib_core] [ +0.000023] ib_unregister_device_and_put+0x34/0x50 [ib_core] [ +0.000020] i40iw_close+0x4b/0x90 [irdma] [ +0.000022] i40e_notify_client_of_netdev_close+0x54/0xc0 [i40e] [ +0.000035] i40e_service_task+0x126/0x190 [i40e] [ +0.000024] process_one_work+0x174/0x340 [ +0.000003] worker_th ---truncated---

CVSS v3
5.5
EG Score
5.5(medium)
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
16.3%
KEV
Not listed

Published

May 20, 2024

Last Modified

May 12, 2026

References (19)

Vendor Advisories for CVE-2024-36004(1)

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

Patch Availability(23)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.116.106) @ jammy2026-05-22ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1047 (5.4.0-1047.51) @ focal2026-05-22ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1065.65) @ jammy2026-05-22ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1112.142) @ focal2026-05-22ubuntu
ubuntulinux-tools-iot (5.4.0.1040.38) @ focal2026-05-22ubuntu
ubuntulinux-tools-aws-edge (5.15.0.1065.71~20.04.1) @ focal2026-05-22ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1068.66) @ jammy2026-05-22ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1058.56) @ jammy2026-05-22ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1065.73~20.04.1) @ focal2026-05-22ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-40.40) @ noble2026-05-22ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1010.10) @ noble2026-05-22ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1010.10) @ noble2026-05-22ubuntu
ubuntulinux-tools-raspi (6.8.0-1009.10) @ noble2026-05-22ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1035.39) @ jammy2026-05-22ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.232.244~16.04.1) @ xenial2026-05-22ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.189.209~18.04.1) @ bionic2026-05-22ubuntu
ubuntulinux-tools-azure-edge (4.15.0.1184.199~16.04.1) @ xenial2026-05-22ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.189.187) @ focal2026-05-22ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.116.116) @ jammy2026-05-22ubuntu
redhatkernel-0:5.14.0-427.66.1.el9_42025-04-30redhat
redhatkernel-rt-0:4.18.0-553.8.1.rt7.349.el8_102024-07-08redhat
redhatkernel-0:4.18.0-553.8.1.el8_102024-07-02redhat
linuxKernel @ 4.19.313—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.

Additional Vendor Advisories

(21)

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 12× in last 7d / 45× 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 120 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2024-36004?
CVE-2024-36004 is a medium vulnerability published on May 20, 2024. In the Linux kernel, the following vulnerability has been resolved: i40e: Do not use WQMEMRECLAIM flag for workqueue Issue reported by customer during SRIOV testing, call trace: When both i40e and the i40iw driver are loaded, a warning in checkflushdependency is being triggered. This seems to be…
When was CVE-2024-36004 disclosed?
CVE-2024-36004 was first published in the National Vulnerability Database on May 20, 2024, with the most recent update on May 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-36004 actively exploited?
CVE-2024-36004 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-36004?
CVE-2024-36004 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-36004?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-36004, 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-36004

Explore →

Is Your Infrastructure Affected by CVE-2024-36004?

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

Start Free Scan →Browse All CVEs