<?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>Mon, 28 Sep 2026 09:08:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90280 — phy: qcom: qmp-usb: Fix possible NULL-deref on early runtime suspend</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-90280</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;phy: qcom: qmp-usb: Fix possible NULL-deref on early runtime suspend&lt;/p&gt;
&lt;p&gt;There is a small window where the runtime suspend callback may run
after pm_runtime_enable() and before pm_runtime_forbid(). In this
case, a crash occurs because runtime suspend/resume dereferences
qmp-&amp;gt;phy pointer, which is not yet initialized:
        `if (!qmp-&amp;gt;phy-&amp;gt;init_count) {`&lt;/p&gt;
&lt;p&gt;This can also happen if user re-enables runtime-pm via the sysfs
attribute before qmp phy is initialized.&lt;/p&gt;
&lt;p&gt;Similarly to other qcom phy drivers, introduce a qmp-&amp;gt;phy_initialized
variable that can be used to avoid relying on the possibly uninitialized
phy pointer.&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;phy: qcom: qmp-usb: Fix possible NULL-deref on early runtime suspend&lt;/p&gt;
&lt;p&gt;There is a small window where the runtime suspend callback may run
after pm_runtime_enable() and before pm_runtime_forbid(). In this
case, a crash occurs because runtime suspend/resume dereferences
qmp-&amp;gt;phy pointer, which is not yet initialized:
        `if (!qmp-&amp;gt;phy-&amp;gt;init_count) {`&lt;/p&gt;
&lt;p&gt;This can also happen if user re-enables runtime-pm via the sysfs
attribute before qmp phy is initialized.&lt;/p&gt;
&lt;p&gt;Similarly to other qcom phy drivers, introduce a qmp-&amp;gt;phy_initialized
variable that can be used to avoid relying on the possibly uninitialized
phy pointer.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-90280</guid>
    </item>
  </channel>
</rss>
