<?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>Wed, 30 Sep 2026 10:41:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98093 — ASoC: fsl_micfil: balance mclk enable/disable</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-98093</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;ASoC: fsl_micfil: balance mclk enable/disable&lt;/p&gt;
&lt;p&gt;hw_params() enables mclk unconditionally and hw_free() disables it
unconditionally, but the PCM core does not guarantee 1:1 pairing:
hw_free() can run without hw_params(), and hw_params() can be called
multiple times from the SETUP state. This triggers an &amp;#34;already
disabled&amp;#34; WARN() in the first case and leaks an enable reference in
the second, leaving the clock ungateable.&lt;/p&gt;
&lt;p&gt;Guard both sides with the existing mclk_flag, as fsl_sai.c does with
mclk_streams.&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;ASoC: fsl_micfil: balance mclk enable/disable&lt;/p&gt;
&lt;p&gt;hw_params() enables mclk unconditionally and hw_free() disables it
unconditionally, but the PCM core does not guarantee 1:1 pairing:
hw_free() can run without hw_params(), and hw_params() can be called
multiple times from the SETUP state. This triggers an &amp;#34;already
disabled&amp;#34; WARN() in the first case and leaks an enable reference in
the second, leaving the clock ungateable.&lt;/p&gt;
&lt;p&gt;Guard both sides with the existing mclk_flag, as fsl_sai.c does with
mclk_streams.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-98093</guid>
    </item>
  </channel>
</rss>
