From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org,
Shivaprasad G Bhat <sbhat@linux.ibm.com>
Cc: npiggin@gmail.com, christophe.leroy@csgroup.eu,
linux-kernel@vger.kernel.org, vaibhav@linux.ibm.com,
vaish123@in.ibm.com, stable@vger.kernel.org
Subject: Re: [PATCH] powerpc/pseries/iommu: Don't unset window if it was never set
Date: Wed, 22 Jan 2025 18:13:57 +0530 [thread overview]
Message-ID: <173754932979.1094869.2005290852678611840.b4-ty@linux.ibm.com> (raw)
In-Reply-To: <173674009556.1559.12487885286848752833.stgit@linux.ibm.com>
On Mon, 13 Jan 2025 03:48:55 +0000, Shivaprasad G Bhat wrote:
> On pSeries, when user attempts to use the same vfio container used by
> different iommu group, the spapr_tce_set_window() returns -EPERM
> and the subsequent cleanup leads to the below crash.
>
> Kernel attempted to read user page (308) - exploit attempt?
> BUG: Kernel NULL pointer dereference on read at 0x00000308
> Faulting instruction address: 0xc0000000001ce358
> Oops: Kernel access of bad area, sig: 11 [#1]
> NIP: c0000000001ce358 LR: c0000000001ce05c CTR: c00000000005add0
> <snip>
> NIP [c0000000001ce358] spapr_tce_unset_window+0x3b8/0x510
> LR [c0000000001ce05c] spapr_tce_unset_window+0xbc/0x510
> Call Trace:
> spapr_tce_unset_window+0xbc/0x510 (unreliable)
> tce_iommu_attach_group+0x24c/0x340 [vfio_iommu_spapr_tce]
> vfio_container_attach_group+0xec/0x240 [vfio]
> vfio_group_fops_unl_ioctl+0x548/0xb00 [vfio]
> sys_ioctl+0x754/0x1580
> system_call_exception+0x13c/0x330
> system_call_vectored_common+0x15c/0x2ec
> <snip>
> --- interrupt: 3000
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/pseries/iommu: Don't unset window if it was never set
https://git.kernel.org/powerpc/c/17391cb2613b82f8c405570fea605af3255ff8d2
Thanks
prev parent reply other threads:[~2025-01-22 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 3:48 Shivaprasad G Bhat
2025-01-22 12:43 ` Madhavan Srinivasan [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=173754932979.1094869.2005290852678611840.b4-ty@linux.ibm.com \
--to=maddy@linux.ibm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=sbhat@linux.ibm.com \
--cc=stable@vger.kernel.org \
--cc=vaibhav@linux.ibm.com \
--cc=vaish123@in.ibm.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®