CVE-2024-56684

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-12-28. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

mailbox: mtk-cmdq: fix wrong use of sizeof in cmdq_get_clocks()

It should be size of the struct clk_bulk_data, not data pointer pass to devm_kcalloc().

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

December 28, 2024

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

mailbox: mtk-cmdq: fix wrong use of sizeof in cmdq_get_clocks() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a9c7cb960fc6e056ebecebd136a127612b15630d
generic

mailbox: mtk-cmdq: fix wrong use of sizeof in cmdq_get_clocks() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/31986fad0cfdda8d8893230da04f5eb0774854d9
generic

mailbox: mtk-cmdq: fix wrong use of sizeof in cmdq_get_clocks() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/271ee263cc8771982809185007181ca10346fe73

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-05-23ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-05-23ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-05-23ubuntu
linuxKernel @ 6.11.11—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.12.3-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.12.3-1—

All Vendor Advisories

(3)

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 5× in last 7d / 28× 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 169 total refreshes for this CVE.

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

What is CVE-2024-56684?
CVE-2024-56684 is a high vulnerability published on December 28, 2024. In the Linux kernel, the following vulnerability has been resolved: mailbox: mtk-cmdq: fix wrong use of sizeof in cmdqgetclocks() It should be size of the struct clkbulkdata, not data pointer pass to devm_kcalloc().
When was CVE-2024-56684 disclosed?
CVE-2024-56684 was first published in the National Vulnerability Database on December 28, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-56684 actively exploited?
CVE-2024-56684 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 87.5% of all scored CVEs.
What is the CVSS score of CVE-2024-56684?
CVE-2024-56684 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-56684?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-56684, 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-56684

Explore →

Is Your Infrastructure Affected by CVE-2024-56684?

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

Start Free Scan →Browse All CVEs