{"uuid": "14bef3e9-9fb4-4505-bad7-1dc7cc41f6e5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56787", "type": "seen", "source": "https://t.me/cvedetector/14710", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56787 - IBM i.MX8M Platform Driver PCIe Pseudo-Retrieval Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56787 \nPublished : Jan. 8, 2025, 6:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nsoc: imx8m: Probe the SoC driver as platform driver  \n  \nWith driver_async_probe=* on kernel command line, the following trace is  \nproduced because on i.MX8M Plus hardware because the soc-imx8m.c driver  \ncalls of_clk_get_by_name() which returns -EPROBE_DEFER because the clock  \ndriver is not yet probed. This was not detected during regular testing  \nwithout driver_async_probe.  \n  \nConvert the SoC code to platform driver and instantiate a platform device  \nin its current device_initcall() to probe the platform driver. Rework  \n.soc_revision callback to always return valid error code and return SoC  \nrevision via parameter. This way, if anything in the .soc_revision callback  \nreturn -EPROBE_DEFER, it gets propagated to .probe and the .probe will get  \nretried later.  \n  \n\"  \n------------[ cut here ]------------  \nWARNING: CPU: 1 PID: 1 at drivers/soc/imx/soc-imx8m.c:115 imx8mm_soc_revision+0xdc/0x180  \nCPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.11.0-next-20240924-00002-g2062bb554dea #603  \nHardware name: DH electronics i.MX8M Plus DHCOM Premium Developer Kit (3) (DT)  \npstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)  \npc : imx8mm_soc_revision+0xdc/0x180  \nlr : imx8mm_soc_revision+0xd0/0x180  \nsp : ffff8000821fbcc0  \nx29: ffff8000821fbce0 x28: 0000000000000000 x27: ffff800081810120  \nx26: ffff8000818a9970 x25: 0000000000000006 x24: 0000000000824311  \nx23: ffff8000817f42c8 x22: ffff0000df8be210 x21: fffffffffffffdfb  \nx20: ffff800082780000 x19: 0000000000000001 x18: ffffffffffffffff  \nx17: ffff800081fff418 x16: ffff8000823e1000 x15: ffff0000c03b65e8  \nx14: ffff0000c00051b0 x13: ffff800082790000 x12: 0000000000000801  \nx11: ffff80008278ffff x10: ffff80008209d3a6 x9 : ffff80008062e95c  \nx8 : ffff8000821fb9a0 x7 : 0000000000000000 x6 : 00000000000080e3  \nx5 : ffff0000df8c03d8 x4 : 0000000000000000 x3 : 0000000000000000  \nx2 : 0000000000000000 x1 : fffffffffffffdfb x0 : fffffffffffffdfb  \nCall trace:  \n imx8mm_soc_revision+0xdc/0x180  \n imx8_soc_init+0xb0/0x1e0  \n do_one_initcall+0x94/0x1a8  \n kernel_init_freeable+0x240/0x2a8  \n kernel_init+0x28/0x140  \n ret_from_fork+0x10/0x20  \n---[ end trace 0000000000000000 ]---  \nSoC: i.MX8MP revision 1.1  \n\" \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-08T19:59:51.000000Z"}