<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 10:11:20 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-46706 — tty: serial: fsl_lpuart: mark last busy before uart_add_one_port</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-46706</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tty: serial: fsl_lpuart: mark last busy before uart_add_one_port&lt;/p&gt;
&lt;p&gt;With &amp;#34;earlycon initcall_debug=1 loglevel=8&amp;#34; 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.&lt;/p&gt;
&lt;p&gt;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
     |-&amp;gt; bus_probe_device
           |-&amp;gt;device_initial_probe
	           |-&amp;gt;__device_attach
                         |-&amp;gt; pm_runtime_get_sync(dev-&amp;gt;parent);
			 |-&amp;gt; pm_request_idle(dev);
			 |-&amp;gt; pm_runtime_put(dev-&amp;gt;parent);&lt;/p&gt;
&lt;p&gt;So in the end, before normal console ready, the lpuart get runtime
suspended. And earlycon putchar will hang.&lt;/p&gt;
&lt;p&gt;To address the issue, mark last busy just after pm_runtime_enable,
three seconds is long enough to switch from bootconsole to normal
console.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tty: serial: fsl_lpuart: mark last busy before uart_add_one_port&lt;/p&gt;
&lt;p&gt;With &amp;#34;earlycon initcall_debug=1 loglevel=8&amp;#34; 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.&lt;/p&gt;
&lt;p&gt;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
     |-&amp;gt; bus_probe_device
           |-&amp;gt;device_initial_probe
	           |-&amp;gt;__device_attach
                         |-&amp;gt; pm_runtime_get_sync(dev-&amp;gt;parent);
			 |-&amp;gt; pm_request_idle(dev);
			 |-&amp;gt; pm_runtime_put(dev-&amp;gt;parent);&lt;/p&gt;
&lt;p&gt;So in the end, before normal console ready, the lpuart get runtime
suspended. And earlycon putchar will hang.&lt;/p&gt;
&lt;p&gt;To address the issue, mark last busy just after pm_runtime_enable,
three seconds is long enough to switch from bootconsole to normal
console.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-46706</guid>
    </item>
  </channel>
</rss>
