<?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 08:09:34 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-90116</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-90116</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-90116</guid>
    </item>
    <item>
      <title>fkie_cve-2026-90116</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-90116</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ALSA: mtpav: shut down output timer before card teardown&lt;/p&gt;
&lt;p&gt;snd_mtpav_output_timer() rearms chip-&amp;gt;timer while holding
chip-&amp;gt;spinlock and accesses the card-private mtpav state.&lt;/p&gt;
&lt;p&gt;snd_mtpav_free() currently takes the same lock and calls
timer_delete() when the timer is active. This only removes a
pending timer; it does not wait for a callback that is already
running and does not prevent the callback from rearming the timer.&lt;/p&gt;
&lt;p&gt;A callback running on another CPU can therefore continue after
snd_mtpav_free() releases the lock and access the card-private
state while the card is being torn down. It can also rearm the
timer after timer_delete() has returned.&lt;/p&gt;
&lt;p&gt;Call timer_shutdown_sync() without holding chip-&amp;gt;spinlock. This
waits for any running callback to finish and prevents further
rearming before the card-private mtpav state is released.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ALSA: mtpav: shut down output timer before card teardown&lt;/p&gt;
&lt;p&gt;snd_mtpav_output_timer() rearms chip-&amp;gt;timer while holding
chip-&amp;gt;spinlock and accesses the card-private mtpav state.&lt;/p&gt;
&lt;p&gt;snd_mtpav_free() currently takes the same lock and calls
timer_delete() when the timer is active. This only removes a
pending timer; it does not wait for a callback that is already
running and does not prevent the callback from rearming the timer.&lt;/p&gt;
&lt;p&gt;A callback running on another CPU can therefore continue after
snd_mtpav_free() releases the lock and access the card-private
state while the card is being torn down. It can also rearm the
timer after timer_delete() has returned.&lt;/p&gt;
&lt;p&gt;Call timer_shutdown_sync() without holding chip-&amp;gt;spinlock. This
waits for any running callback to finish and prevents further
rearming before the card-private mtpav state is released.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-90116</guid>
    </item>
    <item>
      <title>GHSA-f6xw-5hrw-vj32</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-f6xw-5hrw-vj32</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ALSA: mtpav: shut down output timer before card teardown&lt;/p&gt;
&lt;p&gt;snd_mtpav_output_timer() rearms chip-&amp;gt;timer while holding
chip-&amp;gt;spinlock and accesses the card-private mtpav state.&lt;/p&gt;
&lt;p&gt;snd_mtpav_free() currently takes the same lock and calls
timer_delete() when the timer is active. This only removes a
pending timer; it does not wait for a callback that is already
running and does not prevent the callback from rearming the timer.&lt;/p&gt;
&lt;p&gt;A callback running on another CPU can therefore continue after
snd_mtpav_free() releases the lock and access the card-private
state while the card is being torn down. It can also rearm the
timer after timer_delete() has returned.&lt;/p&gt;
&lt;p&gt;Call timer_shutdown_sync() without holding chip-&amp;gt;spinlock. This
waits for any running callback to finish and prevents further
rearming before the card-private mtpav state is released.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ALSA: mtpav: shut down output timer before card teardown&lt;/p&gt;
&lt;p&gt;snd_mtpav_output_timer() rearms chip-&amp;gt;timer while holding
chip-&amp;gt;spinlock and accesses the card-private mtpav state.&lt;/p&gt;
&lt;p&gt;snd_mtpav_free() currently takes the same lock and calls
timer_delete() when the timer is active. This only removes a
pending timer; it does not wait for a callback that is already
running and does not prevent the callback from rearming the timer.&lt;/p&gt;
&lt;p&gt;A callback running on another CPU can therefore continue after
snd_mtpav_free() releases the lock and access the card-private
state while the card is being torn down. It can also rearm the
timer after timer_delete() has returned.&lt;/p&gt;
&lt;p&gt;Call timer_shutdown_sync() without holding chip-&amp;gt;spinlock. This
waits for any running callback to finish and prevents further
rearming before the card-private mtpav state is released.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-f6xw-5hrw-vj32</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11880-1 — kernel-devel-7.2.7-1.1 on GA media</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-90116</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-90116</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ALSA: mtpav: shut down output timer before card teardown snd_mtpav_output_timer() rearms chip-&amp;gt;timer while holding chip-&amp;gt;spinlock and accesses the card-private mtpav state. snd_mtpav_free() currently takes the same lock and calls timer_delete() when the timer is active. This only removes a pending timer; it does not wait for a callback that is already running and does not prevent the callback from rearming the timer. A callback running on another CPU can therefore continue after snd_mtpav_free() releases the lock and access the card-private state while the card is being torn down. It can also rearm the timer after timer_delete() has returned. Call timer_shutdown_sync() without holding chip-&amp;gt;spinlock. This waits for any running callback to finish and prevents further rearming before the card-private mtpav state is released.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ALSA: mtpav: shut down output timer before card teardown snd_mtpav_output_timer() rearms chip-&amp;gt;timer while holding chip-&amp;gt;spinlock and accesses the card-private mtpav state. snd_mtpav_free() currently takes the same lock and calls timer_delete() when the timer is active. This only removes a pending timer; it does not wait for a callback that is already running and does not prevent the callback from rearming the timer. A callback running on another CPU can therefore continue after snd_mtpav_free() releases the lock and access the card-private state while the card is being torn down. It can also rearm the timer after timer_delete() has returned. Call timer_shutdown_sync() without holding chip-&amp;gt;spinlock. This waits for any running callback to finish and prevents further rearming before the card-private mtpav state is released.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-90116</guid>
    </item>
  </channel>
</rss>
