From: Lizhi Hou <lizhi.hou@amd.com>
To: Max Zhen <max.zhen@amd.com>, <ogabbay@kernel.org>,
<quic_jhugo@quicinc.com>, <dri-devel@lists.freedesktop.org>,
<mario.limonciello@amd.com>, <karol.wachowski@linux.intel.com>
Cc: <linux-kernel@vger.kernel.org>, <sonal.santan@amd.com>
Subject: Re: [PATCH V1] accel/amdxdna: Fix potential NULL pointer access in amdxdna_gem_vmap()
Date: Tue, 7 Jul 2026 12:38:21 -0700 [thread overview]
Message-ID: <da8a2cf1-b6ce-ec02-1105-3a72cce0e747@amd.com> (raw)
In-Reply-To: <1ce38058-6773-4784-95ea-0c48af4a0b4c@amd.com>
On 7/7/26 10:29, Max Zhen wrote:
>
>
> On 7/7/2026 Tue 10:23, Lizhi Hou wrote:
>> If the heap BO was never vmapped before its handle was closed and the
>> user then vmaps the dev BO (which triggers amdxdna_gem_vmap(heap_bo)),
>> and drm_gem_vmap fails — NULL pointer dereference at abo->client->xdna.
>>
>> Fix it by get xdna pointer through to_xdna_dev(to_gobj(abo)->dev).
>>
>> Fixes: d76856beb4a4 ("accel/amdxdna: Refactor GEM BO handling and add
>> helper APIs for address retrieval")
>> Signed-off-by: Lizhi Hou <lizhi.hou@amd.com>
> Reviewed-by: Max Zhen <max.zhen@amd.com>
Thanks a lot for reviewing the patch. Sashiko bot reports other places
which can trigger abo->client NULL pointer dereference. I will create a
V2 patch which fix those places as well.
Lizhi
>> ---
>> drivers/accel/amdxdna/amdxdna_gem.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/accel/amdxdna/amdxdna_gem.c
>> b/drivers/accel/amdxdna/amdxdna_gem.c
>> index 64c7d82713b0..5033a0e5c6ab 100644
>> --- a/drivers/accel/amdxdna/amdxdna_gem.c
>> +++ b/drivers/accel/amdxdna/amdxdna_gem.c
>> @@ -198,6 +198,7 @@ amdxdna_gem_destroy_obj(struct amdxdna_gem_obj *abo)
>> */
>> void *amdxdna_gem_vmap(struct amdxdna_gem_obj *abo)
>> {
>> + struct amdxdna_dev *xdna = to_xdna_dev(to_gobj(abo)->dev);
>> struct iosys_map map = IOSYS_MAP_INIT_VADDR(NULL);
>> int ret;
>> @@ -210,7 +211,7 @@ void *amdxdna_gem_vmap(struct amdxdna_gem_obj
>> *abo)
>> if (!abo->mem.kva) {
>> ret = drm_gem_vmap(to_gobj(abo), &map);
>> if (ret)
>> - XDNA_ERR(abo->client->xdna, "Vmap bo failed, ret %d", ret);
>> + XDNA_ERR(xdna, "Vmap bo failed, ret %d", ret);
>> else
>> abo->mem.kva = map.vaddr;
>> }
>
prev parent reply other threads:[~2026-07-07 19:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 17:23 [PATCH V1] accel/amdxdna: Fix potential NULL pointer access in amdxdna_gem_vmap() Lizhi Hou
2026-07-07 17:29 ` Max Zhen
2026-07-07 19:38 ` Lizhi Hou [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=da8a2cf1-b6ce-ec02-1105-3a72cce0e747@amd.com \
--to=lizhi.hou@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=karol.wachowski@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=max.zhen@amd.com \
--cc=ogabbay@kernel.org \
--cc=quic_jhugo@quicinc.com \
--cc=sonal.santan@amd.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