<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T04:53:16.866044+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-90116</id>
    <title>CVE-2026-90116 — ALSA: mtpav: shut down output timer before card teardown</title>
    <updated>2026-09-29T04:53:16.883622+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ALSA: mtpav: shut down output timer before card teardown</p>
<p>snd_mtpav_output_timer() rearms chip-&gt;timer while holding
chip-&gt;spinlock and accesses the card-private mtpav state.</p>
<p>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.</p>
<p>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.</p>
<p>Call timer_shutdown_sync() without holding chip-&gt;spinlock. This
waits for any running callback to finish and prevents further
rearming before the card-private mtpav state is released.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-90116"/>
  </entry>
</feed>
