<?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-10-01T10:20:32.994069+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-2024-58084</id>
    <title>CVE-2024-58084 — firmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool()</title>
    <updated>2026-10-01T10:20:33.012053+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>firmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool()</p>
<p>Commit 2e4955167ec5 ("firmware: qcom: scm: Fix __scm and waitq
completion variable initialization") introduced a write barrier in probe
function to store global '__scm' variable.  We all known barriers are
paired (see memory-barriers.txt: "Note that write barriers should
normally be paired with read or address-dependency barriers"), therefore
accessing it from concurrent contexts requires read barrier.  Previous
commit added such barrier in qcom_scm_is_available(), so let's use that
directly.</p>
<p>Lack of this read barrier can result in fetching stale '__scm' variable
value, NULL, and dereferencing it.</p>
<p>Note that barrier in qcom_scm_is_available() satisfies here the control
dependency.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2024-58084"/>
  </entry>
</feed>
