From: Matthew Auld <matthew.auld@intel.com>
To: Francois Dugast <francois.dugast@intel.com>,
intel-xe@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org, Sashiko <sashiko-bot@kernel.org>
Subject: Re: [PATCH v3 1/5] gpu/buddy: Fix use-after-free in split_block() call sites
Date: Mon, 18 May 2026 16:38:08 +0100 [thread overview]
Message-ID: <c4b26104-41c8-4e32-b7a7-aa6b5063985f@intel.com> (raw)
In-Reply-To: <20260518141446.124508-2-francois.dugast@intel.com>
On 18/05/2026 15:14, Francois Dugast wrote:
> When split_block() fails it returns before calling mark_split(), leaving
> the block in the FREE state and still linked in the rbtree. The four
> err_undo paths then call __gpu_buddy_free() without first removing the
> block from the tree, which leads to two distinct bugs:
>
> - If the buddy is also free, __gpu_buddy_free() merges the two siblings
> by calling gpu_block_free(mm, block) while block->rb is still linked
> in the tree. Any subsequent rbtree traversal will follow the now-
> dangling pointer, causing a use-after-free.
>
> - In alloc_from_freetree(), where there is no buddy guard,
> __gpu_buddy_free() always reaches mark_free() -> rbtree_insert() with
> block still in the tree, corrupting the rbtree.
>
> The same pattern is already used correctly in __force_merge(): call
> rbtree_remove() to unlink the block before handing it to
> __gpu_buddy_free(). Apply the same fix to all four err_undo sites.
>
> Reported-by: Sashiko <sashiko-bot@kernel.org>
> Signed-off-by: Francois Dugast <francois.dugast@intel.com>
> Assisted-by: GitHub Copilot:claude-sonnet-4.6
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
> ---
> drivers/gpu/buddy.c | 16 ++++++++++++----
> 1 file changed, 12 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/buddy.c b/drivers/gpu/buddy.c
> index eb1457376307..dac2027bb64a 100644
> --- a/drivers/gpu/buddy.c
> +++ b/drivers/gpu/buddy.c
> @@ -737,8 +737,10 @@ __alloc_range_bias(struct gpu_buddy *mm,
> buddy = __get_buddy(block);
> if (buddy &&
> (gpu_buddy_block_is_free(block) &&
> - gpu_buddy_block_is_free(buddy)))
> + gpu_buddy_block_is_free(buddy))) {
> + rbtree_remove(mm, block);
> __gpu_buddy_free(mm, block, false);
> + }
> return ERR_PTR(err);
> }
>
> @@ -847,8 +849,10 @@ alloc_from_freetree(struct gpu_buddy *mm,
> return block;
>
> err_undo:
> - if (tmp != order)
> + if (tmp != order) {
> + rbtree_remove(mm, block);
> __gpu_buddy_free(mm, block, false);
> + }
> return ERR_PTR(err);
> }
>
> @@ -968,8 +972,10 @@ gpu_buddy_offset_aligned_allocation(struct gpu_buddy *mm,
> buddy = __get_buddy(block);
> if (buddy &&
> (gpu_buddy_block_is_free(block) &&
> - gpu_buddy_block_is_free(buddy)))
> + gpu_buddy_block_is_free(buddy))) {
> + rbtree_remove(mm, block);
> __gpu_buddy_free(mm, block, false);
> + }
> return ERR_PTR(err);
> }
>
> @@ -1054,8 +1060,10 @@ static int __alloc_range(struct gpu_buddy *mm,
> buddy = __get_buddy(block);
> if (buddy &&
> (gpu_buddy_block_is_free(block) &&
> - gpu_buddy_block_is_free(buddy)))
> + gpu_buddy_block_is_free(buddy))) {
> + rbtree_remove(mm, block);
> __gpu_buddy_free(mm, block, false);
> + }
>
> err_free:
> if (err == -ENOSPC && total_allocated_on_err) {
next prev parent reply other threads:[~2026-05-18 15:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 14:14 [PATCH v3 0/5] gpu/buddy: Per-order free and used block scoreboards Francois Dugast
2026-05-18 14:14 ` [PATCH v3 1/5] gpu/buddy: Fix use-after-free in split_block() call sites Francois Dugast
2026-05-18 15:38 ` Matthew Auld [this message]
2026-05-18 15:55 ` Matthew Auld
2026-05-20 10:58 ` Francois Dugast
2026-05-21 16:18 ` Matthew Auld
2026-05-18 14:14 ` [PATCH v3 2/5] gpu/buddy: Remove redundant condition in alloc_from_freetree() error path Francois Dugast
2026-05-18 14:14 ` [PATCH v3 3/5] gpu/buddy: Introduce __gpu_buddy_undo_splits() helper Francois Dugast
2026-05-18 15:57 ` Matthew Auld
2026-05-18 14:14 ` [PATCH v3 4/5] gpu/buddy: Track per-order free blocks with a scoreboard Francois Dugast
2026-05-18 15:58 ` Matthew Auld
2026-05-18 14:14 ` [PATCH v3 5/5] gpu/buddy: Track per-order used " Francois Dugast
2026-05-18 16:02 ` Matthew Auld
2026-05-19 15:40 ` Francois Dugast
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=c4b26104-41c8-4e32-b7a7-aa6b5063985f@intel.com \
--to=matthew.auld@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=francois.dugast@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=sashiko-bot@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