CVE-2024-46706: tty: serial: fsl_lpuart: mark last busy before uart_add_one_port

Published Sep 13, 2024
·
Updated

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

10 affected componentsFixes available
Linux Linux kernel>=6.2<6.6.48
Linux Linux kernel>=6.7<6.10.7
Linux Linux kernel=6.11-rc1
Linux Linux kernel=6.11-rc2
Linux Linux kernel=6.11-rc3
Microsoft azl3 kernel 6.6.47.1-1
Microsoft azl3 kernel 6.6.51.1-5
debian/linux<6.10.7-1
6.10.7-1
debian/linux<6.10.7-1
6.10.7-1
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.12-17.2.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1
  2. Compensating control

    In the fsl_lpuart driver, mark the device last busy immediately after pm_runtime_enable and before uart_add_one_port, preventing runtime suspend before switching from the boot console to the normal console.

Event History

Sep 13, 2024
CVE Published
via MITRE·06:27 AM
Data Sourced
via MITRE·06:27 AM
Description
Data Sourced
via OSV·07:15 AM
DescriptionSeverityAffected Software
Oct 16, 2024
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203