<?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 17:32:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72257 — ASoC: qcom: q6apm: fix NULL pointer dereference in graph_callback</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72257</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: qcom: q6apm: fix NULL pointer dereference in graph_callback&lt;/p&gt;
&lt;p&gt;When q6apm_free_fragments() is called it frees rx_data.buf/tx_data.buf
and sets them to NULL under graph-&amp;gt;lock. A late DSP buffer-done response
can race with this: graph_callback() passes the !graph-&amp;gt;ar_graph guard
(not yet NULL), acquires the lock, but then dereferences a now-NULL buf
pointer to read buf[token].phys, crashing at virtual address 0x10.&lt;/p&gt;
&lt;p&gt;Add a NULL check for buf inside the mutex-protected section in both the
write-done (DATA_CMD_RSP_WR_SH_MEM_EP_DATA_BUFFER_DONE_V2) and
read-done (DATA_CMD_RSP_RD_SH_MEM_EP_DATA_BUFFER_V2) handlers and bail
out cleanly if buffers have already been freed.&lt;/p&gt;
&lt;p&gt;This problem is only shown up recently while apr bus was updated to
process the commands per service rather from single global queue.&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: qcom: q6apm: fix NULL pointer dereference in graph_callback&lt;/p&gt;
&lt;p&gt;When q6apm_free_fragments() is called it frees rx_data.buf/tx_data.buf
and sets them to NULL under graph-&amp;gt;lock. A late DSP buffer-done response
can race with this: graph_callback() passes the !graph-&amp;gt;ar_graph guard
(not yet NULL), acquires the lock, but then dereferences a now-NULL buf
pointer to read buf[token].phys, crashing at virtual address 0x10.&lt;/p&gt;
&lt;p&gt;Add a NULL check for buf inside the mutex-protected section in both the
write-done (DATA_CMD_RSP_WR_SH_MEM_EP_DATA_BUFFER_DONE_V2) and
read-done (DATA_CMD_RSP_RD_SH_MEM_EP_DATA_BUFFER_V2) handlers and bail
out cleanly if buffers have already been freed.&lt;/p&gt;
&lt;p&gt;This problem is only shown up recently while apr bus was updated to
process the commands per service rather from single global queue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72257</guid>
    </item>
  </channel>
</rss>
