{"vulnerability": "CVE-2024-57926", "sightings": [{"uuid": "81ec6a4f-cd05-4d97-ba08-9704bba24a84", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57926", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/2334", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-57926\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/mediatek: Set private->all_drm_private[i]->drm to NULL if mtk_drm_bind returns err\n\nThe pointer need to be set to NULL, otherwise KASAN complains about\nuse-after-free. Because in mtk_drm_bind, all private's drm are set\nas follows.\n\nprivate->all_drm_private[i]->drm = drm;\n\nAnd drm will be released by drm_dev_put in case mtk_drm_kms_init returns\nfailure. However, the shutdown path still accesses the previous allocated\nmemory in drm_atomic_helper_shutdown.\n\n[   84.874820] watchdog: watchdog0: watchdog did not stop!\n[   86.512054] ==================================================================\n[   86.513162] BUG: KASAN: use-after-free in drm_atomic_helper_shutdown+0x33c/0x378\n[   86.514258] Read of size 8 at addr ffff0000d46fc068 by task shutdown/1\n[   86.515213]\n[   86.515455] CPU: 1 UID: 0 PID: 1 Comm: shutdown Not tainted 6.13.0-rc1-mtk+gfa1a78e5d24b-dirty #55\n[   86.516752] Hardware name: Unknown Product/Unknown Product, BIOS 2022.10 10/01/2022\n[   86.517960] Call trace:\n[   86.518333]  show_stack+0x20/0x38 (C)\n[   86.518891]  dump_stack_lvl+0x90/0xd0\n[   86.519443]  print_report+0xf8/0x5b0\n[   86.519985]  kasan_report+0xb4/0x100\n[   86.520526]  __asan_report_load8_noabort+0x20/0x30\n[   86.521240]  drm_atomic_helper_shutdown+0x33c/0x378\n[   86.521966]  mtk_drm_shutdown+0x54/0x80\n[   86.522546]  platform_shutdown+0x64/0x90\n[   86.523137]  device_shutdown+0x260/0x5b8\n[   86.523728]  kernel_restart+0x78/0xf0\n[   86.524282]  __do_sys_reboot+0x258/0x2f0\n[   86.524871]  __arm64_sys_reboot+0x90/0xd8\n[   86.525473]  invoke_syscall+0x74/0x268\n[   86.526041]  el0_svc_common.constprop.0+0xb0/0x240\n[   86.526751]  do_el0_svc+0x4c/0x70\n[   86.527251]  el0_svc+0x4c/0xc0\n[   86.527719]  el0t_64_sync_handler+0x144/0x168\n[   86.528367]  el0t_64_sync+0x198/0x1a0\n[   86.528920]\n[   86.529157] The buggy address belongs to the physical page:\n[   86.529972] page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xffff0000d46fd4d0 pfn:0x1146fc\n[   86.531319] flags: 0xbfffc0000000000(node=0|zone=2|lastcpupid=0xffff)\n[   86.532267] raw: 0bfffc0000000000 0000000000000000 dead000000000122 0000000000000000\n[   86.533390] raw: ffff0000d46fd4d0 0000000000000000 00000000ffffffff 0000000000000000\n[   86.534511] page dumped because: kasan: bad access detected\n[   86.535323]\n[   86.535559] Memory state around the buggy address:\n[   86.536265]  ffff0000d46fbf00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n[   86.537314]  ffff0000d46fbf80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n[   86.538363] >ffff0000d46fc000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n[   86.544733]                                                           ^\n[   86.551057]  ffff0000d46fc080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n[   86.557510]  ffff0000d46fc100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n[   86.563928] ==================================================================\n[   86.571093] Disabling lock debugging due to kernel taint\n[   86.577642] Unable to handle kernel paging request at virtual address e0e9c0920000000b\n[   86.581834] KASAN: maybe wild-memory-access in range [0x0752049000000058-0x075204900000005f]\n...\n\ud83d\udccf Published: 2025-01-19T11:52:43.915Z\n\ud83d\udccf Modified: 2025-01-19T11:52:43.915Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/7083b93e9755d60f0c2bcaa9d064308108280534\n2. https://git.kernel.org/stable/c/078b2ff7da200b7532398e668eef723ad40fb516\n3. https://git.kernel.org/stable/c/36684e9d88a2e2401ae26715a2e217cb4295cea7", "creation_timestamp": "2025-01-19T11:58:27.000000Z"}, {"uuid": "9a45c816-8db2-4fee-b54b-684b65886b77", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57926", "type": "seen", "source": "https://t.me/cvedetector/15850", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57926 - Mediatek Linux Kernel DRM Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-57926 \nPublished : Jan. 19, 2025, 12:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/mediatek: Set private->all_drm_private[i]->drm to NULL if mtk_drm_bind returns err  \n  \nThe pointer need to be set to NULL, otherwise KASAN complains about  \nuse-after-free. Because in mtk_drm_bind, all private's drm are set  \nas follows.  \n  \nprivate->all_drm_private[i]->drm = drm;  \n  \nAnd drm will be released by drm_dev_put in case mtk_drm_kms_init returns  \nfailure. However, the shutdown path still accesses the previous allocated  \nmemory in drm_atomic_helper_shutdown.  \n  \n[   84.874820] watchdog: watchdog0: watchdog did not stop!  \n[   86.512054] ==================================================================  \n[   86.513162] BUG: KASAN: use-after-free in drm_atomic_helper_shutdown+0x33c/0x378  \n[   86.514258] Read of size 8 at addr ffff0000d46fc068 by task shutdown/1  \n[   86.515213]  \n[   86.515455] CPU: 1 UID: 0 PID: 1 Comm: shutdown Not tainted 6.13.0-rc1-mtk+gfa1a78e5d24b-dirty #55  \n[   86.516752] Hardware name: Unknown Product/Unknown Product, BIOS 2022.10 10/01/2022  \n[   86.517960] Call trace:  \n[   86.518333]  show_stack+0x20/0x38 (C)  \n[   86.518891]  dump_stack_lvl+0x90/0xd0  \n[   86.519443]  print_report+0xf8/0x5b0  \n[   86.519985]  kasan_report+0xb4/0x100  \n[   86.520526]  __asan_report_load8_noabort+0x20/0x30  \n[   86.521240]  drm_atomic_helper_shutdown+0x33c/0x378  \n[   86.521966]  mtk_drm_shutdown+0x54/0x80  \n[   86.522546]  platform_shutdown+0x64/0x90  \n[   86.523137]  device_shutdown+0x260/0x5b8  \n[   86.523728]  kernel_restart+0x78/0xf0  \n[   86.524282]  __do_sys_reboot+0x258/0x2f0  \n[   86.524871]  __arm64_sys_reboot+0x90/0xd8  \n[   86.525473]  invoke_syscall+0x74/0x268  \n[   86.526041]  el0_svc_common.constprop.0+0xb0/0x240  \n[   86.526751]  do_el0_svc+0x4c/0x70  \n[   86.527251]  el0_svc+0x4c/0xc0  \n[   86.527719]  el0t_64_sync_handler+0x144/0x168  \n[   86.528367]  el0t_64_sync+0x198/0x1a0  \n[   86.528920]  \n[   86.529157] The buggy address belongs to the physical page:  \n[   86.529972] page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xffff0000d46fd4d0 pfn:0x1146fc  \n[   86.531319] flags: 0xbfffc0000000000(node=0|zone=2|lastcpupid=0xffff)  \n[   86.532267] raw: 0bfffc0000000000 0000000000000000 dead000000000122 0000000000000000  \n[   86.533390] raw: ffff0000d46fd4d0 0000000000000000 00000000ffffffff 0000000000000000  \n[   86.534511] page dumped because: kasan: bad access detected  \n[   86.535323]  \n[   86.535559] Memory state around the buggy address:  \n[   86.536265]  ffff0000d46fbf00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  \n[   86.537314]  ffff0000d46fbf80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  \n[   86.538363] >ffff0000d46fc000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  \n[   86.544733]                                                           ^  \n[   86.551057]  ffff0000d46fc080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  \n[   86.557510]  ffff0000d46fc100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  \n[   86.563928] ==================================================================  \n[   86.571093] Disabling lock debugging due to kernel taint  \n[   86.577642] Unable to handle kernel paging request at virtual address e0e9c0920000000b  \n[   86.581834] KASAN: maybe wild-memory-access in range [0x0752049000000058-0x075204900000005f]  \n... \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"19 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-19T13:58:24.000000Z"}, {"uuid": "c1d5d1fc-a0e5-4806-95c8-c91a291057a7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57926", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lg3sip63o627", "content": "", "creation_timestamp": "2025-01-19T12:16:34.432626Z"}]}