<?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-29T18:05:15.261254+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-2025-23134</id>
    <title>CVE-2025-23134 — ALSA: timer: Don't take register_mutex with copy_from/to_user()</title>
    <updated>2026-09-29T18:05:16.469523+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: timer: Don't take register_mutex with copy_from/to_user()</p>
<p>The infamous mmap_lock taken in copy_from/to_user() can be often
problematic when it's called inside another mutex, as they might lead
to deadlocks.</p>
<p>In the case of ALSA timer code, the bad pattern is with
guard(mutex)(&amp;register_mutex) that covers copy_from/to_user() -- which
was mistakenly introduced at converting to guard(), and it had been
carefully worked around in the past.</p>
<p>This patch fixes those pieces simply by moving copy_from/to_user() out
of the register mutex lock again.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-23134"/>
  </entry>
</feed>
