CVE-2024-56787

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-01-08. NVD baseline CVSS 5.5; sources differ by 0.0.

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

A fix is available — apply it.

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

soc: imx8m: Probe the SoC driver as platform driver

With driver_async_probe=* on kernel command line, the following trace is produced because on i.MX8M Plus hardware because the soc-imx8m.c driver calls of_clk_get_by_name() which returns -EPROBE_DEFER because the clock driver is not yet probed. This was not detected during regular testing without driver_async_probe.

Convert the SoC code to platform driver and instantiate a platform device in its current device_initcall() to probe the platform driver. Rework .soc_revision callback to always return valid error code and return SoC revision via parameter. This way, if anything in the .soc_revision callback return -EPROBE_DEFER, it gets propagated to .probe and the .probe will get retried later.

" ------------[ cut here ]------------ WARNING: CPU: 1 PID: 1 at drivers/soc/imx/soc-imx8m.c:115 imx8mm_soc_revision+0xdc/0x180 CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.11.0-next-20240924-00002-g2062bb554dea #603 Hardware name: DH electronics i.MX8M Plus DHCOM Premium Developer Kit (3) (DT) pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : imx8mm_soc_revision+0xdc/0x180 lr : imx8mm_soc_revision+0xd0/0x180 sp : ffff8000821fbcc0 x29: ffff8000821fbce0 x28: 0000000000000000 x27: ffff800081810120 x26: ffff8000818a9970 x25: 0000000000000006 x24: 0000000000824311 x23: ffff8000817f42c8 x22: ffff0000df8be210 x21: fffffffffffffdfb x20: ffff800082780000 x19: 0000000000000001 x18: ffffffffffffffff x17: ffff800081fff418 x16: ffff8000823e1000 x15: ffff0000c03b65e8 x14: ffff0000c00051b0 x13: ffff800082790000 x12: 0000000000000801 x11: ffff80008278ffff x10: ffff80008209d3a6 x9 : ffff80008062e95c x8 : ffff8000821fb9a0 x7 : 0000000000000000 x6 : 00000000000080e3 x5 : ffff0000df8c03d8 x4 : 0000000000000000 x3 : 0000000000000000 x2 : 0000000000000000 x1 : fffffffffffffdfb x0 : fffffffffffffdfb Call trace: imx8mm_soc_revision+0xdc/0x180 imx8_soc_init+0xb0/0x1e0 do_one_initcall+0x94/0x1a8 kernel_init_freeable+0x240/0x2a8 kernel_init+0x28/0x140 ret_from_fork+0x10/0x20 ---[ end trace 0000000000000000 ]--- SoC: i.MX8MP revision 1.1 "

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 PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

January 8, 2025

Last Modified

November 3, 2025

References (6)

Patch Availability(26)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-21.21) @ oracular2026-05-30ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1017.17) @ noble2026-05-30ubuntu
ubuntulinux-tools-lowlatency-64k (6.11.0-1011.12) @ oracular2026-05-30ubuntu
ubuntulinux-tools-lowlatency-hwe-24.04-edge (6.11.0-1011.12~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-kvm (5.15.0.1076.72) @ jammy2026-05-30ubuntu
ubuntulinux-tools-realtime (5.15.0.1080.83) @ jammy2026-05-30ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.135.133) @ jammy2026-05-30ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1044.48) @ jammy2026-05-30ubuntu
ubuntulinux-tools-nvidia-tegra-rt (5.15.0.1033.33) @ jammy2026-05-30ubuntu
ubuntulinux-tools-gcp-fips (5.15.0.1079.69) @ jammy2026-05-30ubuntu
ubuntulinux-tools-raspi (6.11.0-1010.10) @ oracular2026-05-30ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.136.147~20.04.1) @ focal2026-05-30ubuntu
ubuntulinux-tools-azure-fde-edge (5.15.0.1086.95~20.04.1.61) @ focal2026-05-30ubuntu
ubuntulinux-virtual (6.8.0-58.60) @ noble2026-05-30ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1028.30~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1074.77~20.04.1) @ focal2026-05-30ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1077.83~20.04.1) @ focal2026-05-30ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1010.12) @ noble2026-05-30ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1027.29~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.8.1-1020.21) @ noble2026-05-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-58.60~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1081.90~20.04.1) @ focal2026-05-30ubuntu
ubuntulinux-tools-raspi-realtime (6.8.0-2023.24) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1014.15) @ noble2026-05-30ubuntu
ubuntulinux-tools-raspi (6.8.0-1028.32) @ noble2026-05-30ubuntu
linuxKernel @ 5.15.174—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.

All Vendor Advisories

(25)

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 7× in last 7d / 38× 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 111 total refreshes for this CVE.

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

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2024-56787?
CVE-2024-56787 is a medium vulnerability published on January 8, 2025. In the Linux kernel, the following vulnerability has been resolved: soc: imx8m: Probe the SoC driver as platform driver With driverasyncprobe=* on kernel command line, the following trace is produced because on i.MX8M Plus hardware because the soc-imx8m.c driver calls ofclkgetbyname() which returns…
When was CVE-2024-56787 disclosed?
CVE-2024-56787 was first published in the National Vulnerability Database on January 8, 2025, with the most recent update on November 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-56787 actively exploited?
CVE-2024-56787 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 89.1% of all scored CVEs.
What is the CVSS score of CVE-2024-56787?
CVE-2024-56787 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-56787?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-56787, 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-56787

Explore →

Is Your Infrastructure Affected by CVE-2024-56787?

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

Start Free Scan →Browse All CVEs