<?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://db.gcve.eu</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>Thu, 19 Nov 2026 17:44:29 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-58084 — firmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool()</title>
      <link>https://db.gcve.eu/vuln/cve-2024-58084</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;firmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool()&lt;/p&gt;
&lt;p&gt;Commit 2e4955167ec5 (&amp;#34;firmware: qcom: scm: Fix __scm and waitq
completion variable initialization&amp;#34;) introduced a write barrier in probe
function to store global &amp;#39;__scm&amp;#39; variable.  We all known barriers are
paired (see memory-barriers.txt: &amp;#34;Note that write barriers should
normally be paired with read or address-dependency barriers&amp;#34;), therefore
accessing it from concurrent contexts requires read barrier.  Previous
commit added such barrier in qcom_scm_is_available(), so let&amp;#39;s use that
directly.&lt;/p&gt;
&lt;p&gt;Lack of this read barrier can result in fetching stale &amp;#39;__scm&amp;#39; variable
value, NULL, and dereferencing it.&lt;/p&gt;
&lt;p&gt;Note that barrier in qcom_scm_is_available() satisfies here the control
dependency.&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;firmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool()&lt;/p&gt;
&lt;p&gt;Commit 2e4955167ec5 (&amp;#34;firmware: qcom: scm: Fix __scm and waitq
completion variable initialization&amp;#34;) introduced a write barrier in probe
function to store global &amp;#39;__scm&amp;#39; variable.  We all known barriers are
paired (see memory-barriers.txt: &amp;#34;Note that write barriers should
normally be paired with read or address-dependency barriers&amp;#34;), therefore
accessing it from concurrent contexts requires read barrier.  Previous
commit added such barrier in qcom_scm_is_available(), so let&amp;#39;s use that
directly.&lt;/p&gt;
&lt;p&gt;Lack of this read barrier can result in fetching stale &amp;#39;__scm&amp;#39; variable
value, NULL, and dereferencing it.&lt;/p&gt;
&lt;p&gt;Note that barrier in qcom_scm_is_available() satisfies here the control
dependency.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2024-58084</guid>
    </item>
    <item>
      <title>USN-7521-1 — linux, linux-azure, linux-azure-6.11, linux-gcp, linux-gcp-6.11, linux-hwe-6.11, linux-oem-6.11, linux-raspi, linux-rea…</title>
      <link>https://db.gcve.eu/vuln/usn-7521-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-azure-6.11, Ubuntu:24.04:LTS: linux-gcp-6.11, Ubuntu:24.04:LTS: linux-hwe-6.11, Ubuntu:24.04:LTS: linux-oem-6.11&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - PowerPC architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - Network block device driver;
  - Bluetooth drivers;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Hardware crypto device drivers;
  - FireWire subsystem;
  - EFI core;
  - Qualcomm firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - I2C subsystem;
  - I3C subsystem;
  - InfiniBand drivers;
  - Input Device (Mouse) drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media drivers;
  - NVIDIA Tegra memory controller driver;
  - Fastrpc Driver;
  - Network drivers;
  - Operating Performance Points (OPP) driver;
  - PCI subsystem;
  - x86 platform drivers;
  - PPS (Pulse Per Second) driver;
  - PTP clock framework;
  - Remote Processor subsystem;
  - Real Time Clock drivers;
  - S/390 drivers;
  - SCSI subsystem;
  - QCOM SoC drivers;
  - SPI subsystem;
  - Media staging drivers;
  - Trusted Execution Environment drivers;
  - TTY drivers;
  - UFS subsystem;
  - USB Device Class drivers;
  - USB core drivers;
  - USB Gadget drivers;
  - USB Host Controller drivers;
  - Framebuffer layer;
  - File systems infrastructure;
  - BTRFS file system;
  - Ceph distributed fi…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-azure-6.11, Ubuntu:24.04:LTS: linux-gcp-6.11, Ubuntu:24.04:LTS: linux-hwe-6.11, Ubuntu:24.04:LTS: linux-oem-6.11&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - PowerPC architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - Network block device driver;
  - Bluetooth drivers;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Hardware crypto device drivers;
  - FireWire subsystem;
  - EFI core;
  - Qualcomm firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - I2C subsystem;
  - I3C subsystem;
  - InfiniBand drivers;
  - Input Device (Mouse) drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media drivers;
  - NVIDIA Tegra memory controller driver;
  - Fastrpc Driver;
  - Network drivers;
  - Operating Performance Points (OPP) driver;
  - PCI subsystem;
  - x86 platform drivers;
  - PPS (Pulse Per Second) driver;
  - PTP clock framework;
  - Remote Processor subsystem;
  - Real Time Clock drivers;
  - S/390 drivers;
  - SCSI subsystem;
  - QCOM SoC drivers;
  - SPI subsystem;
  - Media staging drivers;
  - Trusted Execution Environment drivers;
  - TTY drivers;
  - UFS subsystem;
  - USB Device Class drivers;
  - USB core drivers;
  - USB Gadget drivers;
  - USB Host Controller drivers;
  - Framebuffer layer;
  - File systems infrastructure;
  - BTRFS file system;
  - Ceph distributed fi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-7521-1</guid>
    </item>
  </channel>
</rss>
