<?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:31:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21739 — scsi: ufs: core: Fix use-after free in init error and remove paths</title>
      <link>https://db.gcve.eu/vuln/cve-2025-21739</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;scsi: ufs: core: Fix use-after free in init error and remove paths&lt;/p&gt;
&lt;p&gt;devm_blk_crypto_profile_init() registers a cleanup handler to run when
the associated (platform-) device is being released. For UFS, the
crypto private data and pointers are stored as part of the ufs_hba&amp;#39;s
data structure &amp;#39;struct ufs_hba::crypto_profile&amp;#39;. This structure is
allocated as part of the underlying ufshcd and therefore Scsi_host
allocation.&lt;/p&gt;
&lt;p&gt;During driver release or during error handling in ufshcd_pltfrm_init(),
this structure is released as part of ufshcd_dealloc_host() before the
(platform-) device associated with the crypto call above is released.
Once this device is released, the crypto cleanup code will run, using
the just-released &amp;#39;struct ufs_hba::crypto_profile&amp;#39;. This causes a
use-after-free situation:&lt;/p&gt;
&lt;p&gt;Call trace:
   kfree+0x60/0x2d8 (P)
   kvfree+0x44/0x60
   blk_crypto_profile_destroy_callback+0x28/0x70
   devm_action_release+0x1c/0x30
   release_nodes+0x6c/0x108
   devres_release_all+0x98/0x100
   device_unbind_cleanup+0x20/0x70
   really_probe+0x218/0x2d0&lt;/p&gt;
&lt;p&gt;In other words, the initialisation code flow is:&lt;/p&gt;
&lt;p&gt;platform-device probe
    ufshcd_pltfrm_init()
      ufshcd_alloc_host()
        scsi_host_alloc()
          allocation of struct ufs_hba
          creation of scsi-host devices
    devm_blk_crypto_profile_init()
      devm registration of cleanup handler using platform-device&lt;/p&gt;
&lt;p&gt;and during error handling of ufshcd_p…&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;scsi: ufs: core: Fix use-after free in init error and remove paths&lt;/p&gt;
&lt;p&gt;devm_blk_crypto_profile_init() registers a cleanup handler to run when
the associated (platform-) device is being released. For UFS, the
crypto private data and pointers are stored as part of the ufs_hba&amp;#39;s
data structure &amp;#39;struct ufs_hba::crypto_profile&amp;#39;. This structure is
allocated as part of the underlying ufshcd and therefore Scsi_host
allocation.&lt;/p&gt;
&lt;p&gt;During driver release or during error handling in ufshcd_pltfrm_init(),
this structure is released as part of ufshcd_dealloc_host() before the
(platform-) device associated with the crypto call above is released.
Once this device is released, the crypto cleanup code will run, using
the just-released &amp;#39;struct ufs_hba::crypto_profile&amp;#39;. This causes a
use-after-free situation:&lt;/p&gt;
&lt;p&gt;Call trace:
   kfree+0x60/0x2d8 (P)
   kvfree+0x44/0x60
   blk_crypto_profile_destroy_callback+0x28/0x70
   devm_action_release+0x1c/0x30
   release_nodes+0x6c/0x108
   devres_release_all+0x98/0x100
   device_unbind_cleanup+0x20/0x70
   really_probe+0x218/0x2d0&lt;/p&gt;
&lt;p&gt;In other words, the initialisation code flow is:&lt;/p&gt;
&lt;p&gt;platform-device probe
    ufshcd_pltfrm_init()
      ufshcd_alloc_host()
        scsi_host_alloc()
          allocation of struct ufs_hba
          creation of scsi-host devices
    devm_blk_crypto_profile_init()
      devm registration of cleanup handler using platform-device&lt;/p&gt;
&lt;p&gt;and during error handling of ufshcd_p…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2025-21739</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>
