CVE-2024-46706
Last modified
CVE-2024-46706 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: tty: serial: fsl_lpuart: mark last busy before uart_add_one_port With "earlycon initcall_debug=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 uart_add_one_port, a child device serial ctrl will added and probed with its pm runtime enabled(see serial_ctrl.c). The runtime suspend call path is: device_add |-> bus_probe_device |->device_initial_probe |->__device_attach |-> pm_runtime_get_sync(dev->parent); |-> pm_request_idle(dev); |-> pm_runtime_put(dev->parent); So in the end, before normal console ready, the lpuart get runtime suspended. EPSS estimates a 0.21% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: tty: serial: fsl_lpuart: mark last busy before uart_add_one_port With "earlycon initcall_debug=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 uart_add_one_port, a child device serial ctrl will added and probed with its pm runtime enabled(see serial_ctrl.c). The runtime suspend call path is: device_add |-> bus_probe_device |->device_initial_probe |->__device_attach |-> pm_runtime_get_sync(dev->parent); |-> pm_request_idle(dev); |-> pm_runtime_put(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 pm_runtime_enable, three seconds is long enough to switch from bootconsole to normal console.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.2, < 6.6.48 | — |
| Linux | Linux Kernel | >= 6.7, < 6.10.7 | — |
| Linux | Linux Kernel | 6.11 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2024-46706?
How severe is CVE-2024-46706?
How do I fix CVE-2024-46706?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-46700Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2024-46701In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-46702In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-46703In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-46704In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2024-46705In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-46707In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-46708In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-46709In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-4671Use after free in Visuals in Google Chrome prior to 124.0.63…9.6
- CVE-2024-46710In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2024-46711In the Linux kernel, the following vulnerability has been re…4.7
Are you affected by CVE-2024-46706?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
