From: Jani Nikula <jani.nikula@linux.intel.com>
To: Zheng Wang <1002992920@qq.com>, gregkh@linuxfoundation.org
Cc: alex000young@gmail.com, security@kernel.org, airlied@linux.ie,
intel-gfx@lists.freedesktop.org, hackerzheng666@gmail.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gvt: fix double-free bug in split_2MB_gtt_entry
Date: Mon, 19 Sep 2022 12:30:33 +0300 [thread overview]
Message-ID: <87pmfrpv7q.fsf@intel.com> (raw)
In-Reply-To: <tencent_ED24158E83CB9885E8BDD173EB5896B51906@qq.com>
On Mon, 19 Sep 2022, Zheng Wang <1002992920@qq.com> wrote:
> From afe79848cb74cc8e45ab426d13fa2394c87e0422 Mon Sep 17 00:00:00 2001
> From: xmzyshypnc <1002992920@qq.com>
> Date: Fri, 16 Sep 2022 23:48:23 +0800
> Subject: [PATCH] drm/i915/gvt: fix double-free bug in split_2MB_gtt_entry
>
> There is a double-free security bug in split_2MB_gtt_entry.
>
> Here is a calling chain :
> ppgtt_populate_spt->ppgtt_populate_shadow_entry->split_2MB_gtt_entry.
>
> If intel_gvt_dma_map_guest_page failed, it will call
> ppgtt_invalidate_spt, which will finally call ppgtt_free_spt and
> kfree(spt). But the caller does not notice that, and it will call
> ppgtt_free_spt again in error path.
>
> Fix this by only freeing spt in ppgtt_invalidate_spt in good case.
>
> Signed-off-by: xmzyshypnc <1002992920@qq.com>
Please use git send-email. The patch is whitespace broken and line
wrapped, making it unusable.
BR,
Jani.
> ---
> drivers/gpu/drm/i915/gvt/gtt.c | 16 +++++++++-------
> 1 file changed, 9 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gvt/gtt.c b/drivers/gpu/drm/i915/gvt/gtt.c
> index ce0eb03709c3..550519f0acca 100644
> --- a/drivers/gpu/drm/i915/gvt/gtt.c
> +++ b/drivers/gpu/drm/i915/gvt/gtt.c
> @@ -959,7 +959,7 @@ static inline int ppgtt_put_spt(struct
> intel_vgpu_ppgtt_spt *spt)
> return atomic_dec_return(&spt->refcount);
> }
>
> -static int ppgtt_invalidate_spt(struct intel_vgpu_ppgtt_spt *spt);
> +static int ppgtt_invalidate_spt(struct intel_vgpu_ppgtt_spt *spt, int
> is_error);
>
> static int ppgtt_invalidate_spt_by_shadow_entry(struct intel_vgpu *vgpu,
> struct intel_gvt_gtt_entry *e)
> @@ -995,7 +995,7 @@ static int
> ppgtt_invalidate_spt_by_shadow_entry(struct intel_vgpu *vgpu,
> ops->get_pfn(e));
> return -ENXIO;
> }
> - return ppgtt_invalidate_spt(s);
> + return ppgtt_invalidate_spt(s, 0);
> }
>
> static inline void ppgtt_invalidate_pte(struct intel_vgpu_ppgtt_spt *spt,
> @@ -1016,7 +1016,7 @@ static inline void ppgtt_invalidate_pte(struct
> intel_vgpu_ppgtt_spt *spt,
> intel_gvt_dma_unmap_guest_page(vgpu, pfn << PAGE_SHIFT);
> }
>
> -static int ppgtt_invalidate_spt(struct intel_vgpu_ppgtt_spt *spt)
> +static int ppgtt_invalidate_spt(struct intel_vgpu_ppgtt_spt *spt, int
> is_error)
> {
> struct intel_vgpu *vgpu = spt->vgpu;
> struct intel_gvt_gtt_entry e;
> @@ -1059,9 +1059,11 @@ static int ppgtt_invalidate_spt(struct
> intel_vgpu_ppgtt_spt *spt)
> }
> }
>
> - trace_spt_change(spt->vgpu->id, "release", spt,
> + if (!is_error) {
> + trace_spt_change(spt->vgpu->id, "release", spt,
> spt->guest_page.gfn, spt->shadow_page.type);
> - ppgtt_free_spt(spt);
> + ppgtt_free_spt(spt);
> + }
> return 0;
> fail:
> gvt_vgpu_err("fail: shadow page %p shadow entry 0x%llx type %d\n",
> @@ -1215,7 +1217,7 @@ static int split_2MB_gtt_entry(struct intel_vgpu
> *vgpu,
> ret = intel_gvt_dma_map_guest_page(vgpu, start_gfn + sub_index,
> PAGE_SIZE, &dma_addr);
> if (ret) {
> - ppgtt_invalidate_spt(spt);
> + ppgtt_invalidate_spt(spt, 1);
> return ret;
> }
> sub_se.val64 = se->val64;
> @@ -1393,7 +1395,7 @@ static int ppgtt_handle_guest_entry_removal(struct
> intel_vgpu_ppgtt_spt *spt,
> ret = -ENXIO;
> goto fail;
> }
> - ret = ppgtt_invalidate_spt(s);
> + ret = ppgtt_invalidate_spt(s, 0);
> if (ret)
> goto fail;
> } else {
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Zheng Wang <1002992920@qq.com>, gregkh@linuxfoundation.org
Cc: alex000young@gmail.com, security@kernel.org,
tvrtko.ursulin@linux.intel.com, airlied@linux.ie,
intel-gfx@lists.freedesktop.org, hackerzheng666@gmail.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/i915/gvt: fix double-free bug in split_2MB_gtt_entry
Date: Mon, 19 Sep 2022 12:30:33 +0300 [thread overview]
Message-ID: <87pmfrpv7q.fsf@intel.com> (raw)
In-Reply-To: <tencent_ED24158E83CB9885E8BDD173EB5896B51906@qq.com>
On Mon, 19 Sep 2022, Zheng Wang <1002992920@qq.com> wrote:
> From afe79848cb74cc8e45ab426d13fa2394c87e0422 Mon Sep 17 00:00:00 2001
> From: xmzyshypnc <1002992920@qq.com>
> Date: Fri, 16 Sep 2022 23:48:23 +0800
> Subject: [PATCH] drm/i915/gvt: fix double-free bug in split_2MB_gtt_entry
>
> There is a double-free security bug in split_2MB_gtt_entry.
>
> Here is a calling chain :
> ppgtt_populate_spt->ppgtt_populate_shadow_entry->split_2MB_gtt_entry.
>
> If intel_gvt_dma_map_guest_page failed, it will call
> ppgtt_invalidate_spt, which will finally call ppgtt_free_spt and
> kfree(spt). But the caller does not notice that, and it will call
> ppgtt_free_spt again in error path.
>
> Fix this by only freeing spt in ppgtt_invalidate_spt in good case.
>
> Signed-off-by: xmzyshypnc <1002992920@qq.com>
Please use git send-email. The patch is whitespace broken and line
wrapped, making it unusable.
BR,
Jani.
> ---
> drivers/gpu/drm/i915/gvt/gtt.c | 16 +++++++++-------
> 1 file changed, 9 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gvt/gtt.c b/drivers/gpu/drm/i915/gvt/gtt.c
> index ce0eb03709c3..550519f0acca 100644
> --- a/drivers/gpu/drm/i915/gvt/gtt.c
> +++ b/drivers/gpu/drm/i915/gvt/gtt.c
> @@ -959,7 +959,7 @@ static inline int ppgtt_put_spt(struct
> intel_vgpu_ppgtt_spt *spt)
> return atomic_dec_return(&spt->refcount);
> }
>
> -static int ppgtt_invalidate_spt(struct intel_vgpu_ppgtt_spt *spt);
> +static int ppgtt_invalidate_spt(struct intel_vgpu_ppgtt_spt *spt, int
> is_error);
>
> static int ppgtt_invalidate_spt_by_shadow_entry(struct intel_vgpu *vgpu,
> struct intel_gvt_gtt_entry *e)
> @@ -995,7 +995,7 @@ static int
> ppgtt_invalidate_spt_by_shadow_entry(struct intel_vgpu *vgpu,
> ops->get_pfn(e));
> return -ENXIO;
> }
> - return ppgtt_invalidate_spt(s);
> + return ppgtt_invalidate_spt(s, 0);
> }
>
> static inline void ppgtt_invalidate_pte(struct intel_vgpu_ppgtt_spt *spt,
> @@ -1016,7 +1016,7 @@ static inline void ppgtt_invalidate_pte(struct
> intel_vgpu_ppgtt_spt *spt,
> intel_gvt_dma_unmap_guest_page(vgpu, pfn << PAGE_SHIFT);
> }
>
> -static int ppgtt_invalidate_spt(struct intel_vgpu_ppgtt_spt *spt)
> +static int ppgtt_invalidate_spt(struct intel_vgpu_ppgtt_spt *spt, int
> is_error)
> {
> struct intel_vgpu *vgpu = spt->vgpu;
> struct intel_gvt_gtt_entry e;
> @@ -1059,9 +1059,11 @@ static int ppgtt_invalidate_spt(struct
> intel_vgpu_ppgtt_spt *spt)
> }
> }
>
> - trace_spt_change(spt->vgpu->id, "release", spt,
> + if (!is_error) {
> + trace_spt_change(spt->vgpu->id, "release", spt,
> spt->guest_page.gfn, spt->shadow_page.type);
> - ppgtt_free_spt(spt);
> + ppgtt_free_spt(spt);
> + }
> return 0;
> fail:
> gvt_vgpu_err("fail: shadow page %p shadow entry 0x%llx type %d\n",
> @@ -1215,7 +1217,7 @@ static int split_2MB_gtt_entry(struct intel_vgpu
> *vgpu,
> ret = intel_gvt_dma_map_guest_page(vgpu, start_gfn + sub_index,
> PAGE_SIZE, &dma_addr);
> if (ret) {
> - ppgtt_invalidate_spt(spt);
> + ppgtt_invalidate_spt(spt, 1);
> return ret;
> }
> sub_se.val64 = se->val64;
> @@ -1393,7 +1395,7 @@ static int ppgtt_handle_guest_entry_removal(struct
> intel_vgpu_ppgtt_spt *spt,
> ret = -ENXIO;
> goto fail;
> }
> - ret = ppgtt_invalidate_spt(s);
> + ret = ppgtt_invalidate_spt(s, 0);
> if (ret)
> goto fail;
> } else {
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-09-19 9:30 UTC|newest]
Thread overview: 114+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 19:24 [Intel-gfx] [PATCH] drm/i915/gvt: fix double-free bug in split_2MB_gtt_entry Zheng Wang
2022-09-18 19:24 ` Zheng Wang
2022-09-19 9:30 ` Jani Nikula [this message]
2022-09-19 9:30 ` Jani Nikula
2022-09-19 9:55 ` [Intel-gfx] " Zheng Hacker
2022-09-19 9:55 ` Zheng Hacker
2022-09-19 9:55 ` Zheng Hacker
2022-09-21 9:13 ` [Intel-gfx] " Zheng Hacker
2022-09-21 9:13 ` Zheng Hacker
2022-09-21 9:13 ` Zheng Hacker
2022-09-28 3:33 ` [Intel-gfx] [PATCH] drm/i915/gvt: fix double free " Zheng Wang
2022-09-28 3:33 ` Zheng Wang
2022-09-28 3:33 ` Zheng Wang
2022-10-02 14:18 ` [Intel-gfx] " Greg KH
2022-10-02 14:18 ` Greg KH
2022-10-02 14:18 ` Greg KH
2022-10-03 4:36 ` [Intel-gfx] " Zheng Hacker
2022-10-03 4:36 ` Zheng Hacker
2022-10-03 4:36 ` Zheng Hacker
2022-10-06 16:58 ` [Intel-gfx] [PATCH v2] " Zheng Wang
2022-10-06 16:58 ` Zheng Wang
2022-10-06 16:58 ` Zheng Wang
2022-10-06 19:23 ` [Intel-gfx] " Greg KH
2022-10-06 19:23 ` Greg KH
2022-10-06 19:23 ` Greg KH
2022-10-07 0:39 ` [Intel-gfx] " Zheng Hacker
2022-10-07 0:39 ` Zheng Hacker
2022-10-07 0:39 ` Zheng Hacker
2022-10-07 1:37 ` [Intel-gfx] [PATCH v3] " Zheng Wang
2022-10-07 1:37 ` Zheng Wang
2022-10-07 1:37 ` Zheng Wang
2022-10-27 0:01 ` [Intel-gfx] " Dave Airlie
2022-10-27 0:01 ` Dave Airlie
2022-10-27 0:01 ` Dave Airlie
2022-10-27 3:26 ` [Intel-gfx] " Zheng Hacker
2022-10-27 3:26 ` Zheng Hacker
2022-10-27 3:26 ` Zheng Hacker
2022-10-27 5:12 ` [Intel-gfx] " Dave Airlie
2022-10-27 5:12 ` Dave Airlie
2022-10-27 5:12 ` Dave Airlie
2022-10-30 15:10 ` [Intel-gfx] " Zheng Hacker
2022-10-30 15:10 ` Zheng Hacker
2022-10-30 15:10 ` Zheng Hacker
2022-12-15 10:47 ` [Intel-gfx] " Joonas Lahtinen
2022-12-15 10:47 ` Joonas Lahtinen
2022-12-15 11:33 ` [Intel-gfx] " Wang, Zhi A
2022-12-15 11:33 ` Wang, Zhi A
2022-12-15 13:26 ` [Intel-gfx] " Zheng Hacker
2022-12-15 13:26 ` Zheng Hacker
2022-12-15 13:26 ` Zheng Hacker
2022-12-19 7:57 ` [Intel-gfx] " Zheng Wang
2022-12-19 7:57 ` Zheng Wang
2022-12-19 7:57 ` Zheng Wang
2022-12-19 8:22 ` Wang, Zhi A
2022-12-19 8:22 ` Wang, Zhi A
2022-12-19 8:22 ` Wang, Zhi A
2022-12-19 9:21 ` Zheng Wang
2022-12-19 9:21 ` Zheng Wang
2022-12-19 9:21 ` Zheng Wang
2022-12-19 12:46 ` [Intel-gfx] [PATCH v4] [PATCH v4] " Zheng Wang
2022-12-19 12:46 ` Zheng Wang
2022-12-19 12:46 ` Zheng Wang
2022-12-19 12:52 ` [Intel-gfx] [RESEND PATCH " Zheng Wang
2022-12-19 12:52 ` Zheng Wang
2022-12-19 12:52 ` Zheng Wang
2022-12-20 8:22 ` [Intel-gfx] " Zhenyu Wang
2022-12-20 8:22 ` Zhenyu Wang
2022-12-20 8:22 ` Zhenyu Wang
2022-12-20 9:03 ` [Intel-gfx] " Zheng Hacker
2022-12-20 9:03 ` Zheng Hacker
2022-12-20 9:03 ` Zheng Hacker
2022-12-20 9:40 ` [Intel-gfx] [PATCH v5] " Zheng Wang
2022-12-20 9:40 ` Zheng Wang
2022-12-20 9:40 ` Zheng Wang
2022-12-21 2:58 ` [Intel-gfx] " Zhenyu Wang
2022-12-21 2:58 ` Zhenyu Wang
2022-12-21 2:58 ` Zhenyu Wang
2022-12-21 5:01 ` [Intel-gfx] " Zheng Hacker
2022-12-21 5:01 ` Zheng Hacker
2022-12-21 5:01 ` Zheng Hacker
2022-12-29 16:56 ` [Intel-gfx] [PATCH v6] " Zheng Wang
2022-12-29 16:56 ` Zheng Wang
2022-12-29 16:56 ` Zheng Wang
2022-09-19 20:17 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915/gvt: fix double-free bug in split_2MB_gtt_entry (rev2) Patchwork
2022-09-29 18:16 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/gvt: fix double-free bug in split_2MB_gtt_entry (rev3) Patchwork
2022-09-29 18:40 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-09-30 18:41 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-10-10 15:00 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/gvt: fix double-free bug in split_2MB_gtt_entry (rev5) Patchwork
2022-10-10 15:30 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-12-22 12:25 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/gvt: fix double-free bug in split_2MB_gtt_entry (rev8) Patchwork
2022-12-22 12:53 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-12-22 18:13 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-12-29 17:57 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/gvt: fix double-free bug in split_2MB_gtt_entry (rev9) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2022-09-19 11:44 [Intel-gfx] [PATCH] drm/i915/gvt: fix double-free bug in split_2MB_gtt_entry Zheng Wang
[not found] <tencent_E1BBF05904DFB73C478DCD592740AAE0780A@qq.com>
2022-09-05 4:47 ` Zheng Hacker
2022-09-05 6:11 ` Zheng Hacker
2022-09-05 7:35 ` Zheng Hacker
2022-09-05 7:46 ` Zheng Hacker
2022-09-05 8:04 ` Greg KH
2022-09-06 11:36 ` Zheng Hacker
2022-09-07 3:07 ` Zhenyu Wang
2022-09-07 6:47 ` Zheng Hacker
2022-09-08 9:09 ` Zheng Hacker
2022-09-08 9:19 ` Greg KH
2022-09-08 11:59 ` Zheng Hacker
2022-09-16 6:39 ` Zheng Hacker
2022-09-16 6:40 ` Zheng Hacker
2022-09-16 8:25 ` Greg KH
2022-09-16 15:21 ` Zheng Hacker
2022-09-16 15:54 ` Zheng Hacker
2022-09-17 9:08 ` Greg KH
2022-09-17 9:10 ` Zheng Hacker
2022-09-18 17:08 ` =?gb18030?B?s68=?=
2022-09-18 17:17 ` Zheng Hacker
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=87pmfrpv7q.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=1002992920@qq.com \
--cc=airlied@linux.ie \
--cc=alex000young@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=hackerzheng666@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=security@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.