CVE-2024-27004

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-05-01. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2024-24266 (ENISA EUVD) · GHSA-cf9c-p3v8-r72c (GitHub Security Advisories)Source: ENISA EUVD

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:

clk: Get runtime PM before walking tree during disable_unused

Doug reported [1] the following hung task:

INFO: task swapper/0:1 blocked for more than 122 seconds. Not tainted 5.15.149-21875-gf795ebc40eb8 #1 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:swapper/0 state:D stack: 0 pid: 1 ppid: 0 flags:0x00000008 Call trace: __switch_to+0xf4/0x1f4 __schedule+0x418/0xb80 schedule+0x5c/0x10c rpm_resume+0xe0/0x52c rpm_resume+0x178/0x52c __pm_runtime_resume+0x58/0x98 clk_pm_runtime_get+0x30/0xb0 clk_disable_unused_subtree+0x58/0x208 clk_disable_unused_subtree+0x38/0x208 clk_disable_unused_subtree+0x38/0x208 clk_disable_unused_subtree+0x38/0x208 clk_disable_unused_subtree+0x38/0x208 clk_disable_unused+0x4c/0xe4 do_one_initcall+0xcc/0x2d8 do_initcall_level+0xa4/0x148 do_initcalls+0x5c/0x9c do_basic_setup+0x24/0x30 kernel_init_freeable+0xec/0x164 kernel_init+0x28/0x120 ret_from_fork+0x10/0x20 INFO: task kworker/u16:0:9 blocked for more than 122 seconds. Not tainted 5.15.149-21875-gf795ebc40eb8 #1 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/u16:0 state:D stack: 0 pid: 9 ppid: 2 flags:0x00000008 Workqueue: events_unbound deferred_probe_work_func Call trace: __switch_to+0xf4/0x1f4 __schedule+0x418/0xb80 schedule+0x5c/0x10c schedule_preempt_disabled+0x2c/0x48 __mutex_lock+0x238/0x488 __mutex_lock_slowpath+0x1c/0x28 mutex_lock+0x50/0x74 clk_prepare_lock+0x7c/0x9c clk_core_prepare_lock+0x20/0x44 clk_prepare+0x24/0x30 clk_bulk_prepare+0x40/0xb0 mdss_runtime_resume+0x54/0x1c8 pm_generic_runtime_resume+0x30/0x44 __genpd_runtime_resume+0x68/0x7c genpd_runtime_resume+0x108/0x1f4 __rpm_callback+0x84/0x144 rpm_callback+0x30/0x88 rpm_resume+0x1f4/0x52c rpm_resume+0x178/0x52c __pm_runtime_resume+0x58/0x98 __device_attach+0xe0/0x170 device_initial_probe+0x1c/0x28 bus_probe_device+0x3c/0x9c device_add+0x644/0x814 mipi_dsi_device_register_full+0xe4/0x170 devm_mipi_dsi_device_register_full+0x28/0x70 ti_sn_bridge_probe+0x1dc/0x2c0 auxiliary_bus_probe+0x4c/0x94 really_probe+0xcc/0x2c8 __driver_probe_device+0xa8/0x130 driver_probe_device+0x48/0x110 __device_attach_driver+0xa4/0xcc bus_for_each_drv+0x8c/0xd8 __device_attach+0xf8/0x170 device_initial_probe+0x1c/0x28 bus_probe_device+0x3c/0x9c deferred_probe_work_func+0x9c/0xd8 process_one_work+0x148/0x518 worker_thread+0x138/0x350 kthread+0x138/0x1e0 ret_from_fork+0x10/0x20

The first thread is walking the clk tree and calling clk_pm_runtime_get() to power on devices required to read the clk hardware via struct clk_ops::is_enabled(). This thread holds the clk prepare_lock, and is trying to runtime PM resume a device, when it finds that the device is in the process of resuming so the thread schedule()s away waiting for the device to finish resuming before continuing. The second thread is runtime PM resuming the same device, but the runtime resume callback is calling clk_prepare(), trying to grab the prepare_lock waiting on the first thread.

This is a classic ABBA deadlock. To properly fix the deadlock, we must never runtime PM resume or suspend a device with the clk prepare_lock held. Actually doing that is near impossible today because the global prepare_lock would have to be dropped in the middle of the tree, the device runtime PM resumed/suspended, and then the prepare_lock grabbed again to ensure consistency of the clk tree topology. If anything changes with the clk tree in the meantime, we've lost and will need to start the operation all over again.

Luckily, most of the time we're simply incrementing or decrementing the runtime PM count on an active device, so we don't have the chance to schedule away with the prepare_lock held. Let's fix this immediate problem that can be ---truncated---

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 (model v2026.06.15, score date 2026-10-25). 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

May 1, 2024

Last Modified

October 15, 2026

References (13)

Vendor Advisories for CVE-2024-27004(2)

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

Patch Availability(19)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-38.38) @ noble2026-05-22ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.116.116) @ jammy2026-05-22ubuntu
ubuntulinux-tools-nvidia-64k (6.8.0-1009.9) @ noble2026-05-22ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.189.209~18.04.1) @ bionic2026-05-22ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1008.8) @ noble2026-05-22ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1112.142) @ focal2026-05-22ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1047 (5.4.0-1047.51) @ focal2026-05-22ubuntu
ubuntulinux-tools-aws (6.8.0-1011.12) @ noble2026-05-22ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1068.66) @ jammy2026-05-22ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1035.39) @ jammy2026-05-22ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.116.106) @ jammy2026-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-gcp-edge (5.15.0.1065.73~20.04.1) @ focal2026-05-22ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1065.65) @ jammy2026-05-22ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.189.187) @ focal2026-05-22ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1058.56) @ jammy2026-05-22ubuntu
redhatkernel-0:5.14.0-503.11.1.el9_52024-11-12redhat
linuxKernel @ 5.4.275 (fixes >=4.15.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.90-1~bpo11+1 (21 versions)
  • every version up to 6.1.90-1: fixed in 6.1.90-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.9-1: fixed in 6.8.9-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.9-1: fixed in 6.8.9-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(17)

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 8× in last 7d / 40× 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 97 of 229 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 132 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-27004?
CVE-2024-27004 is a medium-severity vulnerability; its CVE record was published on May 1, 2024. In the Linux kernel, the following vulnerability has been resolved: clk: Get runtime PM before walking tree during disable_unused Doug reported [1] the following hung task: INFO: task swapper/0:1 blocked for more than 122 seconds. Not tainted 5.15.149-21875-gf795ebc40eb8 #1 "echo 0 >…
When was the CVE record for CVE-2024-27004 published?
The CVE record for CVE-2024-27004 was published on May 1, 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-27004 actively exploited?
CVE-2024-27004 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-27004?
CVE-2024-27004 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-27004?
A fix for CVE-2024-27004 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-27004 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-27004

Explore →

Is Your Infrastructure Affected by CVE-2024-27004?

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

Book a Demo →Browse All CVEs