CVE-2024-40906

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-38717 (ENISA EUVD) · GHSA-jpp6-vjx7-xmp2 (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:

net/mlx5: Always stop health timer during driver removal

Currently, if teardown_hca fails to execute during driver removal, mlx5 does not stop the health timer. Afterwards, mlx5 continue with driver teardown. This may lead to a UAF bug, which results in page fault Oops[1], since the health timer invokes after resources were freed.

Hence, stop the health monitor even if teardown_hca fails.

[1] mlx5_core 0000:18:00.0: E-Switch: Unload vfs: mode(LEGACY), nvfs(0), necvfs(0), active vports(0) mlx5_core 0000:18:00.0: E-Switch: Disable: mode(LEGACY), nvfs(0), necvfs(0), active vports(0) mlx5_core 0000:18:00.0: E-Switch: Disable: mode(LEGACY), nvfs(0), necvfs(0), active vports(0) mlx5_core 0000:18:00.0: E-Switch: cleanup mlx5_core 0000:18:00.0: wait_func:1155:(pid 1967079): TEARDOWN_HCA(0x103) timeout. Will cause a leak of a command resource mlx5_core 0000:18:00.0: mlx5_function_close:1288:(pid 1967079): tear_down_hca failed, skip cleanup BUG: unable to handle page fault for address: ffffa26487064230 PGD 100c00067 P4D 100c00067 PUD 100e5a067 PMD 105ed7067 PTE 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 0 PID: 0 Comm: swapper/0 Tainted: G OE ------- --- 6.7.0-68.fc38.x86_64 #1 Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0013.121520200651 12/15/2020 RIP: 0010:ioread32be+0x34/0x60 RSP: 0018:ffffa26480003e58 EFLAGS: 00010292 RAX: ffffa26487064200 RBX: ffff9042d08161a0 RCX: ffff904c108222c0 RDX: 000000010bbf1b80 RSI: ffffffffc055ddb0 RDI: ffffa26487064230 RBP: ffff9042d08161a0 R08: 0000000000000022 R09: ffff904c108222e8 R10: 0000000000000004 R11: 0000000000000441 R12: ffffffffc055ddb0 R13: ffffa26487064200 R14: ffffa26480003f00 R15: ffff904c108222c0 FS: 0000000000000000(0000) GS:ffff904c10800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffa26487064230 CR3: 00000002c4420006 CR4: 00000000007706f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: ? __die+0x23/0x70 ? page_fault_oops+0x171/0x4e0 ? exc_page_fault+0x175/0x180 ? asm_exc_page_fault+0x26/0x30 ? __pfx_poll_health+0x10/0x10 [mlx5_core] ? __pfx_poll_health+0x10/0x10 [mlx5_core] ? ioread32be+0x34/0x60 mlx5_health_check_fatal_sensors+0x20/0x100 [mlx5_core] ? __pfx_poll_health+0x10/0x10 [mlx5_core] poll_health+0x42/0x230 [mlx5_core] ? __next_timer_interrupt+0xbc/0x110 ? __pfx_poll_health+0x10/0x10 [mlx5_core] call_timer_fn+0x21/0x130 ? __pfx_poll_health+0x10/0x10 [mlx5_core] __run_timers+0x222/0x2c0 run_timer_softirq+0x1d/0x40 __do_softirq+0xc9/0x2c8 __irq_exit_rcu+0xa6/0xc0 sysvec_apic_timer_interrupt+0x72/0x90 asm_sysvec_apic_timer_interrupt+0x1a/0x20 RIP: 0010:cpuidle_enter_state+0xcc/0x440 ? cpuidle_enter_state+0xbd/0x440 cpuidle_enter+0x2d/0x40 do_idle+0x20d/0x270 cpu_startup_entry+0x2a/0x30 rest_init+0xd0/0xd0 arch_call_rest_init+0xe/0x30 start_kernel+0x709/0xa90 x86_64_start_reservations+0x18/0x30 x86_64_start_kernel+0x96/0xa0 secondary_startup_64_no_verify+0x18f/0x19b ---[ end trace 0000000000000000 ]---

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-27). 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

November 3, 2025

Advisory Details (5)

Auto-updated Oct 11, 2026
Patch available.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4008-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Web page

net/mlx5: Always stop health timer during driver removal - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/mlx5: Always stop health timer during driver removal - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/mlx5: Always stop health timer during driver removal - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/mlx5: Always stop health timer during driver removal - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6ccada6ffb42e0ac75e3db06d41baf5a7f483f8a

Vendor Advisories for CVE-2024-40906(3)

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

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1013.14.1) @ noble2026-10-28ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-44.44) @ noble2026-10-28ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-45.45~22.04.1) @ jammy2026-10-28ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1013.14~22.04.1) @ jammy2026-10-28ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-44.44.1~22.04.1) @ jammy2026-10-28ubuntu
ubuntulinux-tools-azure (6.8.0-1014.16) @ noble2026-10-28ubuntu
ubuntulinux-tools-raspi (6.8.0-1011.12) @ noble2026-10-28ubuntu
redhatkernel-rt-0:4.18.0-553.53.1.rt7.394.el8_102025-05-21redhat
redhatkernel-0:4.18.0-553.53.1.el8_102025-05-21redhat
redhatkernel-0:5.14.0-503.11.1.el9_52024-11-12redhat
linuxKernel @ 6.1.95 (fixes >=6.1.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
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

(7)

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 / 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 96 of 214 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 118 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-40906?
CVE-2024-40906 is a high-severity vulnerability; its CVE record was published on July 12, 2024. In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Always stop health timer during driver removal Currently, if teardown_hca fails to execute during driver removal, mlx5 does not stop the health timer. Afterwards, mlx5 continue with driver teardown. This may lead to a UAF…
When was the CVE record for CVE-2024-40906 published?
The CVE record for CVE-2024-40906 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 November 3, 2025; the record at its source may have been updated since.
Is CVE-2024-40906 actively exploited?
CVE-2024-40906 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-40906?
CVE-2024-40906 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-40906?
A fix for CVE-2024-40906 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-40906 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-40906

Explore →

Is Your Infrastructure Affected by CVE-2024-40906?

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

Book a Demo →Browse All CVEs