mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Joerg Roedel <joro@8bytes.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Kevin Tian <kevin.tian@intel.com>,
	Ethan Milon <ethan.milon@eviden.com>,
	Jason Gunthorpe <jgg@ziepe.ca>,
	Lu Baolu <baolu.lu@linux.intel.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
	Will Deacon <will@kernel.org>,
	iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] iommu/vt-d: Fix UAF on sva unbind with pending IOPFs
Date: Wed, 23 Jul 2025 13:52:52 +0100	[thread overview]
Message-ID: <175327211759.77634.8242308703852038544.b4-ty@kernel.org> (raw)
In-Reply-To: <20250723072045.1853328-1-baolu.lu@linux.intel.com>

On Wed, 23 Jul 2025 15:20:45 +0800, Lu Baolu wrote:
> Commit 17fce9d2336d ("iommu/vt-d: Put iopf enablement in domain attach
> path") disables IOPF on device by removing the device from its IOMMU's
> IOPF queue when the last IOPF-capable domain is detached from the device.
> Unfortunately, it did this in a wrong place where there are still pending
> IOPFs. As a result, a use-after-free error is potentially triggered and
> eventually a kernel panic with a kernel trace similar to the following:
> 
> [...]

Applied to iommu (intel/vt-d), thanks!

[1/1] iommu/vt-d: Fix UAF on sva unbind with pending IOPFs
      https://git.kernel.org/iommu/c/f0b9d31c6edd

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev

      reply	other threads:[~2025-07-23 12:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23  7:20 Lu Baolu
2025-07-23 12:52 ` Will Deacon [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=175327211759.77634.8242308703852038544.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=baolu.lu@linux.intel.com \
    --cc=catalin.marinas@arm.com \
    --cc=ethan.milon@eviden.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=joro@8bytes.org \
    --cc=kernel-team@android.com \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.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

all inboxes | Powered by JetHome®