From: Benjamin Gaignard <benjamin.gaignard@collabora.com>
To: Yibo Tan <lhfff@tju.edu.cn>,
"Joerg Roedel (AMD)" <joro@8bytes.org>,
Will Deacon <will@kernel.org>
Cc: Robin Murphy <robin.murphy@arm.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iommu/vsi: Fix use-after-free during module unload
Date: Tue, 8 Sep 2026 12:40:11 +0200 [thread overview]
Message-ID: <402b9f73-03b0-433b-baa1-01b57038ee31@collabora.com> (raw)
In-Reply-To: <20260907195228.812227-1-lhfff@tju.edu.cn>
Le 07/09/2026 à 21:52, Yibo Tan a écrit :
> iommu_device_register() links the embedded iommu_device into the IOMMU
> core's global device list. The VSI driver can be built as a module, but
> has no remove callback to unregister the device before devres frees the
> containing struct vsi_iommu.
>
> With no attached consumer holding a module reference, unloading
> vsi-iommu.ko succeeds. A later platform device registration enters the
> IOMMU bus notifier and scans the stale list entry. KASAN reports a
> slab-use-after-free in __iommu_probe_device().
>
> The missing unregister operation on driver unbind was also noted during
> review of the driver's fwnode lookup lifetime handling.
>
> Add the missing remove callback. Unregister the IOMMU device and remove
> its sysfs object while the provider is still alive, then force runtime
> suspend and unprepare the clocks acquired during probe. Leave the IRQ
> and other managed resources to devres teardown.
>
> The failure was reproduced with real module load and unload syscalls.
> With the same KASAN kernel, the unmodified driver produced two invalid
> reads from the same freed list entry. The patched driver removed the
> entry, completed the later device registration and produced no KASAN,
> WARNING, Oops or panic.
>
> The remove callback also builds with W=1 for arm64 with
> ARCH_ROCKCHIP=y and CONFIG_PM=y, and for the arm64 COMPILE_TEST path
> with CONFIG_PM=n.
>
> A standalone reproducer, the vulnerable and fixed serial logs, and
> their checksums are available at:
>
> https://github.com/kimaiden1984-boop/linux-vsi-iommu-unload-uaf-reproducer
>
> Fixes: 917ace84b770 ("iommu: Add verisilicon IOMMU driver")
> Link: https://lore.kernel.org/0e405cb3-1227-4ad2-96ff-aa0db3124381@arm.com/
> Cc: stable@vger.kernel.org
> Assisted-by: Codex:GPT-5
> Signed-off-by: Yibo Tan <lhfff@tju.edu.cn>
Reviewed-by: Benjamin Gaignard <benjamin.gaignard@collabora.com>
> ---
> Changes in v2:
> - Drop devm_free_irq() and leave managed IRQ teardown to devres.
> - Re-run the KASAN A/B test and arm64 PM-enabled and PM-disabled builds.
>
> v1: https://lore.kernel.org/all/20260905183834.3447662-1-lhfff@tju.edu.cn/
>
> drivers/iommu/vsi-iommu.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/drivers/iommu/vsi-iommu.c b/drivers/iommu/vsi-iommu.c
> index 42c424496d07..f73bcc82c472 100644
> --- a/drivers/iommu/vsi-iommu.c
> +++ b/drivers/iommu/vsi-iommu.c
> @@ -728,6 +728,16 @@ static int vsi_iommu_probe(struct platform_device *pdev)
> return err;
> }
>
> +static void vsi_iommu_remove(struct platform_device *pdev)
> +{
> + struct vsi_iommu *iommu = platform_get_drvdata(pdev);
> +
> + iommu_device_unregister(&iommu->iommu);
> + iommu_device_sysfs_remove(&iommu->iommu);
> + pm_runtime_force_suspend(&pdev->dev);
> + clk_bulk_unprepare(iommu->num_clocks, iommu->clocks);
> +}
> +
> static void vsi_iommu_shutdown(struct platform_device *pdev)
> {
> struct vsi_iommu *iommu = platform_get_drvdata(pdev);
> @@ -776,6 +786,7 @@ static DEFINE_RUNTIME_DEV_PM_OPS(vsi_iommu_pm_ops,
>
> static struct platform_driver rockchip_vsi_iommu_driver = {
> .probe = vsi_iommu_probe,
> + .remove = vsi_iommu_remove,
> .shutdown = vsi_iommu_shutdown,
> .driver = {
> .name = "vsi_iommu",
prev parent reply other threads:[~2026-09-08 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 18:38 [PATCH v1] " Yibo Tan
2026-09-07 7:30 ` Benjamin Gaignard
2026-09-07 19:22 ` Yibo Tan
2026-09-07 19:52 ` [PATCH v2] " Yibo Tan
2026-09-08 10:40 ` Benjamin Gaignard [this message]
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=402b9f73-03b0-433b-baa1-01b57038ee31@collabora.com \
--to=benjamin.gaignard@collabora.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=lhfff@tju.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
/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
all inboxes | Powered by JetHome®