From: jackysliu <1972843537@qq.com>
To: harry.wentland@amd.com
Cc: 1972843537@qq.com, Austin.Zheng@amd.com, Dillon.Varone@amd.com,
Security@tencent.com, Sung.Lee@amd.com, Wayne.Lin@amd.com,
airlied@gmail.com, alexander.deucher@amd.com, alvin.lee2@amd.com,
amd-gfx@lists.freedesktop.org, aurabindo.pillai@amd.com,
christian.koenig@amd.com, dri-devel@lists.freedesktop.org,
joshua.aberback@amd.com, linux-kernel@vger.kernel.org,
linux@treblig.org, mario.limonciello@amd.com, ryanseto@amd.com,
simona@ffwll.ch, siqueira@igalia.com, sunpeng.li@amd.com
Subject: [PATCH v2] drm/amd/display:fix a Null pointer dereference vulnerability
Date: Fri, 4 Jul 2025 11:16:22 +0800 [thread overview]
Message-ID: <tencent_54FF4252EDFB6533090A491A25EEF3EDBF06@qq.com> (raw)
In-Reply-To: <220f9fb4-45ad-4997-9572-564242737dd4@amd.com>
From: jackysliu <Security@tencent.com>
A null pointer dereference vulnerability exists in the AMD display driver's
(DC module) cleanup function dc_destruct().
When display control context (dc->ctx) construction fails
(due to memory allocation failure), this pointer remains NULL.
During subsequent error handling when dc_destruct() is called,
there's no NULL check before dereferencing the perf_trace member
(dc->ctx->perf_trace),
causing a kernel null pointer dereference crash
Signed-off-by: jackysliu <Security@tencent.com>
---
drivers/gpu/drm/amd/display/dc/core/dc.c | 20 ++++++++++++--------
1 file changed, 12 insertions(+), 8 deletions(-)
diff --git a/drivers/gpu/drm/amd/display/dc/core/dc.c b/drivers/gpu/drm/amd/display/dc/core/dc.c
index 56d011a1323c..393f87cfe74d 100644
--- a/drivers/gpu/drm/amd/display/dc/core/dc.c
+++ b/drivers/gpu/drm/amd/display/dc/core/dc.c
@@ -934,17 +934,21 @@ static void dc_destruct(struct dc *dc)
if (dc->link_srv)
link_destroy_link_service(&dc->link_srv);
- if (dc->ctx->gpio_service)
- dal_gpio_service_destroy(&dc->ctx->gpio_service);
+ if (!dc->ctx) {
+ dm_error("%s: called with NULL ctx\n", __func__);
+ } else {
+ if (dc->ctx->gpio_service)
+ dal_gpio_service_destroy(&dc->ctx->gpio_service);
- if (dc->ctx->created_bios)
- dal_bios_parser_destroy(&dc->ctx->dc_bios);
+ if (dc->ctx->created_bios)
+ dal_bios_parser_destroy(&dc->ctx->dc_bios);
- kfree(dc->ctx->logger);
- dc_perf_trace_destroy(&dc->ctx->perf_trace);
+ kfree(dc->ctx->logger);
+ dc_perf_trace_destroy(&dc->ctx->perf_trace);
- kfree(dc->ctx);
- dc->ctx = NULL;
+ kfree(dc->ctx);
+ dc->ctx = NULL;
+ }
kfree(dc->bw_vbios);
dc->bw_vbios = NULL;
--
2.43.5
next prev parent reply other threads:[~2025-07-04 3:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 3:39 [PATCH] " jackysliu
2025-07-03 15:15 ` Harry Wentland
2025-07-04 3:11 ` jackysliu
2025-07-04 3:16 ` jackysliu [this message]
2025-07-15 10:44 ` [PATCH v2] " Krzysztof Kozlowski
2025-07-15 21:29 ` Mario Limonciello
2025-07-16 3:10 ` [PATCH] scsi:bfa: Double-free vulnerability fix jackysliu
2025-07-16 3:37 ` [PATCH v2] drm/amd/display:fix a Null pointer dereference vulnerability jackysliu
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=tencent_54FF4252EDFB6533090A491A25EEF3EDBF06@qq.com \
--to=1972843537@qq.com \
--cc=Austin.Zheng@amd.com \
--cc=Dillon.Varone@amd.com \
--cc=Security@tencent.com \
--cc=Sung.Lee@amd.com \
--cc=Wayne.Lin@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=alvin.lee2@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=aurabindo.pillai@amd.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=joshua.aberback@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=mario.limonciello@amd.com \
--cc=ryanseto@amd.com \
--cc=simona@ffwll.ch \
--cc=siqueira@igalia.com \
--cc=sunpeng.li@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
all inboxes | Powered by JetHome®