CVE-2024-26854

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2024-04-17. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2024-24116 (ENISA EUVD) · GHSA-gw9v-f3c7-qfqv (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
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.7%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ice: fix uninitialized dplls mutex usage

The pf->dplls.lock mutex is initialized too late, after its first use. Move it to the top of ice_dpll_init. Note that the "err_exit" error path destroys the mutex. And the mutex is the last thing destroyed in ice_dpll_deinit. This fixes the following warning with CONFIG_DEBUG_MUTEXES:

ice 0000:10:00.0: The DDP package was successfully loaded: ICE OS Default Package version 1.3.36.0 ice 0000:10:00.0: 252.048 Gb/s available PCIe bandwidth (16.0 GT/s PCIe x16 link) ice 0000:10:00.0: PTP init successful ------------[ cut here ]------------ DEBUG_LOCKS_WARN_ON(lock->magic != lock) WARNING: CPU: 0 PID: 410 at kernel/locking/mutex.c:587 __mutex_lock+0x773/0xd40 Modules linked in: crct10dif_pclmul crc32_pclmul crc32c_intel polyval_clmulni polyval_generic ice(+) nvme nvme_c> CPU: 0 PID: 410 Comm: kworker/0:4 Not tainted 6.8.0-rc5+ #3 Hardware name: HPE ProLiant DL110 Gen10 Plus/ProLiant DL110 Gen10 Plus, BIOS U56 10/19/2023 Workqueue: events work_for_cpu_fn RIP: 0010:__mutex_lock+0x773/0xd40 Code: c0 0f 84 1d f9 ff ff 44 8b 35 0d 9c 69 01 45 85 f6 0f 85 0d f9 ff ff 48 c7 c6 12 a2 a9 85 48 c7 c7 12 f1 a> RSP: 0018:ff7eb1a3417a7ae0 EFLAGS: 00010286 RAX: 0000000000000000 RBX: 0000000000000002 RCX: 0000000000000000 RDX: 0000000000000002 RSI: ffffffff85ac2bff RDI: 00000000ffffffff RBP: ff7eb1a3417a7b80 R08: 0000000000000000 R09: 00000000ffffbfff R10: ff7eb1a3417a7978 R11: ff32b80f7fd2e568 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: ff32b7f02c50e0d8 FS: 0000000000000000(0000) GS:ff32b80efe800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000055b5852cc000 CR3: 000000003c43a004 CR4: 0000000000771ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: ? __warn+0x84/0x170 ? __mutex_lock+0x773/0xd40 ? report_bug+0x1c7/0x1d0 ? prb_read_valid+0x1b/0x30 ? handle_bug+0x42/0x70 ? exc_invalid_op+0x18/0x70 ? asm_exc_invalid_op+0x1a/0x20 ? __mutex_lock+0x773/0xd40 ? rcu_is_watching+0x11/0x50 ? __kmalloc_node_track_caller+0x346/0x490 ? ice_dpll_lock_status_get+0x28/0x50 [ice] ? __pfx_ice_dpll_lock_status_get+0x10/0x10 [ice] ? ice_dpll_lock_status_get+0x28/0x50 [ice] ice_dpll_lock_status_get+0x28/0x50 [ice] dpll_device_get_one+0x14f/0x2e0 dpll_device_event_send+0x7d/0x150 dpll_device_register+0x124/0x180 ice_dpll_init_dpll+0x7b/0xd0 [ice] ice_dpll_init+0x224/0xa40 [ice] ? _dev_info+0x70/0x90 ice_load+0x468/0x690 [ice] ice_probe+0x75b/0xa10 [ice] ? _raw_spin_unlock_irqrestore+0x4f/0x80 ? process_one_work+0x1a3/0x500 local_pci_probe+0x47/0xa0 work_for_cpu_fn+0x17/0x30 process_one_work+0x20d/0x500 worker_thread+0x1df/0x3e0 ? __pfx_worker_thread+0x10/0x10 kthread+0x103/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x31/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 irq event stamp: 125197 hardirqs last enabled at (125197): [] finish_task_switch.isra.0+0x12d/0x3d0 hardirqs last disabled at (125196): [] __schedule+0xea4/0x19f0 softirqs last enabled at (105334): [] napi_get_frags_check+0x1a/0x60 softirqs last disabled at (105332): [] napi_get_frags_check+0x1a/0x60 ---[ end trace 0000000000000000 ]---

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 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.7%
EPSS %ILE
53rd
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.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% 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

April 17, 2024

Last Modified

March 21, 2025

References (2)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 6.7.10 (fixes >=6.7.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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.12-1: fixed in 6.7.12-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.12-1: fixed in 6.7.12-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 39× 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 209 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 112 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.7% · 53rd percentile
  2. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  3. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  4. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  5. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  6. 2026-10-28 05:11 UTCEG score recompute
  7. 2026-10-28 05:11 UTCGHSA enrichmentGHSA-gw9v-f3c7-qfqv · GitHub severity HIGH · GitHub CVSS 7.5
  8. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  9. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  10. 2026-10-25 17:15 UTCEG score recompute
  11. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  12. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  13. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  14. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  15. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  16. 2026-10-20 20:18 UTCEG score recompute
  17. 2026-10-20 20:18 UTCGHSA enrichmentGHSA-gw9v-f3c7-qfqv · GitHub severity HIGH · GitHub CVSS 7.5
  18. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  19. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  20. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  21. 2026-10-18 07:22 UTCEG score recompute
  22. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  23. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  24. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  25. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
Show 72 more
  1. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  2. 2026-10-12 17:59 UTCEG score recompute
  3. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  4. 2026-10-11 21:23 UTCEG score recompute
  5. 2026-10-11 16:17 UTCEG score recompute
  6. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  7. 2026-10-11 13:36 UTCOSV refresh
  8. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  9. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  10. 2026-10-08 17:07 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  11. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  12. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  13. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  14. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  15. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  16. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  17. 2026-09-30 16:59 UTCEG score recompute
  18. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  19. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  20. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  21. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  22. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  23. 2026-09-22 01:16 UTCOSV refresh
  24. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  25. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  26. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  27. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  28. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  29. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  30. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  31. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  32. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  33. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  34. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  35. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  36. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  37. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  38. 2026-09-02 21:40 UTCOSV refresh
  39. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  40. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  41. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  42. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  43. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  44. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  45. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  46. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  47. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  48. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  49. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  50. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  51. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  52. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  53. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  54. 2026-08-16 12:08 UTCOSV refresh
  55. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  56. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  57. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  58. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  59. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  60. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  61. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  62. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  63. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  64. 2026-08-04 15:08 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  65. 2026-08-04 10:36 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  66. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  67. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  68. 2026-08-01 06:36 UTCOSV refresh
  69. 2026-08-01 04:14 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  70. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  71. 2026-07-30 01:29 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  72. 2026-07-28 15:34 UTCEPSS rescoreEPSS 0.7% · 49th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-26854?
CVE-2024-26854 is a high-severity vulnerability; its CVE record was published on April 17, 2024. In the Linux kernel, the following vulnerability has been resolved: ice: fix uninitialized dplls mutex usage The pf->dplls.lock mutex is initialized too late, after its first use. Move it to the top of ice_dpll_init. Note that the "err_exit" error path destroys the mutex. And the mutex is the last…
When was the CVE record for CVE-2024-26854 published?
The CVE record for CVE-2024-26854 was published on April 17, 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 March 21, 2025; the record at its source may have been updated since.
Is CVE-2024-26854 actively exploited?
CVE-2024-26854 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-26854?
CVE-2024-26854 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2024-26854?
A fix for CVE-2024-26854 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-26854

Explore →

Is Your Infrastructure Affected by CVE-2024-26854?

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

Book a Demo →Browse All CVEs