https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 10:47:57 +0000 https://vulnerability.circl.lu/vuln/cve-2025-21739 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>scsi: ufs: core: Fix use-after free in init error and remove paths</p> <p>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&#39;s data structure &#39;struct ufs_hba::crypto_profile&#39;. This structure is allocated as part of the underlying ufshcd and therefore Scsi_host allocation.</p> <p>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 &#39;struct ufs_hba::crypto_profile&#39;. This causes a use-after-free situation:</p> <p>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</p> <p>In other words, the initialisation code flow is:</p> <p>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</p> <p>and during error handling of ufshcd_p…</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>scsi: ufs: core: Fix use-after free in init error and remove paths</p> <p>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&#39;s data structure &#39;struct ufs_hba::crypto_profile&#39;. This structure is allocated as part of the underlying ufshcd and therefore Scsi_host allocation.</p> <p>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 &#39;struct ufs_hba::crypto_profile&#39;. This causes a use-after-free situation:</p> <p>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</p> <p>In other words, the initialisation code flow is:</p> <p>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</p> <p>and during error handling of ufshcd_p…</p> https://vulnerability.circl.lu/vuln/cve-2025-21739