<?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, 05 Oct 2026 15:26:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-46689 — soc: qcom: cmd-db: Map shared memory as WC, not WB</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-46689</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;soc: qcom: cmd-db: Map shared memory as WC, not WB&lt;/p&gt;
&lt;p&gt;Linux does not write into cmd-db region. This region of memory is write
protected by XPU. XPU may sometime falsely detect clean cache eviction
as &amp;#34;write&amp;#34; into the write protected region leading to secure interrupt
which causes an endless loop somewhere in Trust Zone.&lt;/p&gt;
&lt;p&gt;The only reason it is working right now is because Qualcomm Hypervisor
maps the same region as Non-Cacheable memory in Stage 2 translation
tables. The issue manifests if we want to use another hypervisor (like
Xen or KVM), which does not know anything about those specific mappings.&lt;/p&gt;
&lt;p&gt;Changing the mapping of cmd-db memory from MEMREMAP_WB to MEMREMAP_WT/WC
removes dependency on correct mappings in Stage 2 tables. This patch
fixes the issue by updating the mapping to MEMREMAP_WC.&lt;/p&gt;
&lt;p&gt;I tested this on SA8155P with Xen.&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;soc: qcom: cmd-db: Map shared memory as WC, not WB&lt;/p&gt;
&lt;p&gt;Linux does not write into cmd-db region. This region of memory is write
protected by XPU. XPU may sometime falsely detect clean cache eviction
as &amp;#34;write&amp;#34; into the write protected region leading to secure interrupt
which causes an endless loop somewhere in Trust Zone.&lt;/p&gt;
&lt;p&gt;The only reason it is working right now is because Qualcomm Hypervisor
maps the same region as Non-Cacheable memory in Stage 2 translation
tables. The issue manifests if we want to use another hypervisor (like
Xen or KVM), which does not know anything about those specific mappings.&lt;/p&gt;
&lt;p&gt;Changing the mapping of cmd-db memory from MEMREMAP_WB to MEMREMAP_WT/WC
removes dependency on correct mappings in Stage 2 tables. This patch
fixes the issue by updating the mapping to MEMREMAP_WC.&lt;/p&gt;
&lt;p&gt;I tested this on SA8155P with Xen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-46689</guid>
    </item>
  </channel>
</rss>
