{"vulnerability": "CVE-2024-46706", "sightings": [{"uuid": "6c77079a-497a-4bd5-a667-7f53ed46f1bf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-46706", "type": "seen", "source": "https://t.me/cvedetector/5571", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-46706 - \"Freescale FSL LPUART UARTSTAT Hang on Linux Console Boot\"\", \n  \"Content\": \"CVE ID : CVE-2024-46706 \nPublished : Sept. 13, 2024, 7:15 a.m. | 19\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ntty: serial: fsl_lpuart: mark last busy before uart_add_one_port  \n  \nWith \"earlycon initcall_debug=1 loglevel=8\" in bootargs, kernel  \nsometimes boot hang. It is because normal console still is not ready,  \nbut runtime suspend is called, so early console putchar will hang  \nin waiting TRDE set in UARTSTAT.  \n  \nThe lpuart driver has auto suspend delay set to 3000ms, but during  \nuart_add_one_port, a child device serial ctrl will added and probed with  \nits pm runtime enabled(see serial_ctrl.c).  \nThe runtime suspend call path is:  \ndevice_add  \n     |-> bus_probe_device  \n           |->device_initial_probe  \n            |->__device_attach  \n                         |-> pm_runtime_get_sync(dev->parent);  \n    |-> pm_request_idle(dev);  \n    |-> pm_runtime_put(dev->parent);  \n  \nSo in the end, before normal console ready, the lpuart get runtime  \nsuspended. And earlycon putchar will hang.  \n  \nTo address the issue, mark last busy just after pm_runtime_enable,  \nthree seconds is long enough to switch from bootconsole to normal  \nconsole. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"13 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-13T09:36:14.000000Z"}]}