{"uuid": "30cf731e-1d2c-4c6d-b252-c738b264a05e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48826", "type": "seen", "source": "https://t.me/cvedetector/930", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2022-48826 - In the Linux kernel, the following vulnerability h\", \n  \"Content\": \"CVE ID : CVE-2022-48826 \nPublished : July 16, 2024, 12:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/vc4: Fix deadlock on DSI device attach error  \n  \nDSI device attach to DSI host will be done with host device's lock  \nheld.  \n  \nUn-registering host in \"device attach\" error path (ex: probe retry)  \nwill result in deadlock with below call trace and non operational  \nDSI display.  \n  \nStartup Call trace:  \n[   35.043036]  rt_mutex_slowlock.constprop.21+0x184/0x1b8  \n[   35.043048]  mutex_lock_nested+0x7c/0xc8  \n[   35.043060]  device_del+0x4c/0x3e8  \n[   35.043075]  device_unregister+0x20/0x40  \n[   35.043082]  mipi_dsi_remove_device_fn+0x18/0x28  \n[   35.043093]  device_for_each_child+0x68/0xb0  \n[   35.043105]  mipi_dsi_host_unregister+0x40/0x90  \n[   35.043115]  vc4_dsi_host_attach+0xf0/0x120 [vc4]  \n[   35.043199]  mipi_dsi_attach+0x30/0x48  \n[   35.043209]  tc358762_probe+0x128/0x164 [tc358762]  \n[   35.043225]  mipi_dsi_drv_probe+0x28/0x38  \n[   35.043234]  really_probe+0xc0/0x318  \n[   35.043244]  __driver_probe_device+0x80/0xe8  \n[   35.043254]  driver_probe_device+0xb8/0x118  \n[   35.043263]  __device_attach_driver+0x98/0xe8  \n[   35.043273]  bus_for_each_drv+0x84/0xd8  \n[   35.043281]  __device_attach+0xf0/0x150  \n[   35.043290]  device_initial_probe+0x1c/0x28  \n[   35.043300]  bus_probe_device+0xa4/0xb0  \n[   35.043308]  deferred_probe_work_func+0xa0/0xe0  \n[   35.043318]  process_one_work+0x254/0x700  \n[   35.043330]  worker_thread+0x4c/0x448  \n[   35.043339]  kthread+0x19c/0x1a8  \n[   35.043348]  ret_from_fork+0x10/0x20  \n  \nShutdown Call trace:  \n[  365.565417] Call trace:  \n[  365.565423]  __switch_to+0x148/0x200  \n[  365.565452]  __schedule+0x340/0x9c8  \n[  365.565467]  schedule+0x48/0x110  \n[  365.565479]  schedule_timeout+0x3b0/0x448  \n[  365.565496]  wait_for_completion+0xac/0x138  \n[  365.565509]  __flush_work+0x218/0x4e0  \n[  365.565523]  flush_work+0x1c/0x28  \n[  365.565536]  wait_for_device_probe+0x68/0x158  \n[  365.565550]  device_shutdown+0x24/0x348  \n[  365.565561]  kernel_restart_prepare+0x40/0x50  \n[  365.565578]  kernel_restart+0x20/0x70  \n[  365.565591]  __do_sys_reboot+0x10c/0x220  \n[  365.565605]  __arm64_sys_reboot+0x2c/0x38  \n[  365.565619]  invoke_syscall+0x4c/0x110  \n[  365.565634]  el0_svc_common.constprop.3+0xfc/0x120  \n[  365.565648]  do_el0_svc+0x2c/0x90  \n[  365.565661]  el0_svc+0x4c/0xf0  \n[  365.565671]  el0t_64_sync_handler+0x90/0xb8  \n[  365.565682]  el0t_64_sync+0x180/0x184 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-16T15:26:11.000000Z"}