From: Eric Biggers <ebiggers@kernel.org>
To: "André Draszik" <andre.draszik@linaro.org>
Cc: Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
Bart Van Assche <bvanassche@acm.org>,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Peter Griffin <peter.griffin@linaro.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Mike Snitzer <snitzer@redhat.com>, Jens Axboe <axboe@kernel.dk>,
Ulf Hansson <ulf.hansson@linaro.org>,
Satya Tangirala <satyat@google.com>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Will McVicker <willmcvicker@google.com>,
kernel-team@android.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v4] scsi: ufs: fix use-after free in init error and remove paths
Date: Wed, 29 Jan 2025 17:25:32 -0800 [thread overview]
Message-ID: <20250130012532.GB66821@sol.localdomain> (raw)
In-Reply-To: <20250124-ufshcd-fix-v4-1-c5d0144aae59@linaro.org>
On Fri, Jan 24, 2025 at 03:09:00PM +0000, André Draszik wrote:
> 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's
> data structure 'struct ufs_hba::crypto_profile'. This structure is
> allocated as part of the underlying ufshcd and therefore Scsi_host
> allocation.
>
> 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 'struct ufs_hba::crypto_profile'. This causes a
> use-after-free situation:
>
> 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
>
> In other words, the initialisation code flow is:
>
> 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
>
> and during error handling of ufshcd_pltfrm_init() or during driver
> removal:
>
> ufshcd_dealloc_host()
> scsi_host_put()
> put_device(scsi-host)
> release of struct ufs_hba
> put_device(platform-device)
> crypto cleanup handler
>
> To fix this use-after free, change ufshcd_alloc_host() to register a
> devres action to automatically cleanup the underlying SCSI device on
> ufshcd destruction, without requiring explicit calls to
> ufshcd_dealloc_host(). This way:
>
> * the crypto profile and all other ufs_hba-owned resources are
> destroyed before SCSI (as they've been registered after)
> * a memleak is plugged in tc-dwc-g210-pci.c remove() as a
> side-effect
> * EXPORT_SYMBOL_GPL(ufshcd_dealloc_host) can be removed fully as
> it's not needed anymore
> * no future drivers using ufshcd_alloc_host() could ever forget
> adding the cleanup
>
> Fixes: cb77cb5abe1f ("blk-crypto: rename blk_keyslot_manager to blk_crypto_profile")
> Fixes: d76d9d7d1009 ("scsi: ufs: use devm_blk_ksm_init()")
> Cc: stable@vger.kernel.org
> Signed-off-by: André Draszik <andre.draszik@linaro.org>
Acked-by: Eric Biggers <ebiggers@kernel.org>
- Eric
next prev parent reply other threads:[~2025-01-30 1:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 15:09 [PATCH v4] scsi: ufs: fix use-after free in init error and remove paths André Draszik
2025-01-26 22:00 ` Bean Huo
2025-01-27 5:29 ` Manivannan Sadhasivam
2025-01-30 1:25 ` Eric Biggers [this message]
2025-02-04 3:33 ` Martin K. Petersen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250130012532.GB66821@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=avri.altman@wdc.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=kernel-team@android.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=martin.petersen@oracle.com \
--cc=peter.griffin@linaro.org \
--cc=satyat@google.com \
--cc=snitzer@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tudor.ambarus@linaro.org \
--cc=ulf.hansson@linaro.org \
--cc=willmcvicker@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox