CVE-2024-46706: tty: serial: fsl_lpuart: mark last busy before uart_add_one_port
In the Linux kernel, the following vulnerability has been resolved:
tty: serial: fsllpuart: mark last busy before uartaddoneport
With "earlycon initcalldebug=1 loglevel=8" in bootargs, kernel sometimes boot hang. It is because normal console still is not ready, but runtime suspend is called, so early console putchar will hang in waiting TRDE set in UARTSTAT.
The lpuart driver has auto suspend delay set to 3000ms, but during uartaddoneport, a child device serial ctrl will added and probed with its pm runtime enabled(see serialctrl.c). The runtime suspend call path is: deviceadd |-> busprobedevice |->deviceinitialprobe |->deviceattach |-> pmruntimegetsync(dev->parent); |-> pmrequestidle(dev); |-> pmruntimeput(dev->parent);
So in the end, before normal console ready, the lpuart get runtime suspended. And earlycon putchar will hang.
To address the issue, mark last busy just after pmruntimeenable, three seconds is long enough to switch from bootconsole to normal console.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-46706?
CVE-2024-46706 has not been assigned a CVSS score but is considered a significant vulnerability affecting the Linux kernel.
How do I fix CVE-2024-46706?
To fix CVE-2024-46706, you should upgrade to a patched version of the Linux kernel, specifically versions 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.119-1, or 6.12.11-1.
Which systems are affected by CVE-2024-46706?
CVE-2024-46706 affects various versions of the Linux kernel between 6.2 and 6.10.7 as well as specific release candidates like 6.11-rc1, 6.11-rc2, and 6.11-rc3.
What is the nature of the vulnerability in CVE-2024-46706?
CVE-2024-46706 relates to a boot hang issue in the Linux kernel when certain kernel boot parameters are set.
Is there a workaround for CVE-2024-46706?
There are no documented workarounds for CVE-2024-46706, and upgrading to a fixed version is the recommended solution.