From: Shubham Pushpkar <spushpka@cisco.com>
To: stable@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, deeratho@cisco.com,
Harry Wentland <harry.wentland@amd.com>,
Tom Chung <chiahsuan.chung@amd.com>,
Daniel Wheeler <daniel.wheeler@amd.com>,
Shubham Pushpkar <spushpka@cisco.com>
Subject: [PATCH] drm/amd/display: Check link_index before accessing dc->links[]
Date: Thu, 23 Jan 2025 04:08:22 -0800 [thread overview]
Message-ID: <20250123120822.1983325-1-spushpka@cisco.com> (raw)
From: Alex Hung <alex.hung@amd.com>
commit 8aa2864044b9d13e95fe224f32e808afbf79ecdf ("drm/amd/display:
Check link_index before accessing dc->links[]")
[WHY & HOW]
dc->links[] has max size of MAX_LINKS and NULL is return when trying to
access with out-of-bound index.
This fixes 3 OVERRUN and 1 RESOURCE_LEAK issues reported by Coverity.
Fixes: CVE-2024-46813
Reviewed-by: Harry Wentland <harry.wentland@amd.com>
Acked-by: Tom Chung <chiahsuan.chung@amd.com>
Signed-off-by: Alex Hung <alex.hung@amd.com>
Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
(cherry picked from commit 8aa2864044b9d13e95fe224f32e808afbf79ecdf)
Signed-off-by: Shubham Pushpkar <spushpka@cisco.com>
---
drivers/gpu/drm/amd/display/dc/core/dc_link_exports.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/amd/display/dc/core/dc_link_exports.c b/drivers/gpu/drm/amd/display/dc/core/dc_link_exports.c
index f365773d5714..b5639e88c581 100644
--- a/drivers/gpu/drm/amd/display/dc/core/dc_link_exports.c
+++ b/drivers/gpu/drm/amd/display/dc/core/dc_link_exports.c
@@ -37,6 +37,9 @@
#include "dce/dce_i2c.h"
struct dc_link *dc_get_link_at_index(struct dc *dc, uint32_t link_index)
{
+ if (link_index >= MAX_LINKS)
+ return NULL;
+
return dc->links[link_index];
}
--
2.35.6
next reply other threads:[~2025-01-23 12:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 12:08 Shubham Pushpkar [this message]
2025-01-23 12:10 ` [PATCH] drm/amd/display: Check link_index before accessing dc->links[] kernel test robot
2025-01-23 14:10 ` Greg KH
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=20250123120822.1983325-1-spushpka@cisco.com \
--to=spushpka@cisco.com \
--cc=chiahsuan.chung@amd.com \
--cc=daniel.wheeler@amd.com \
--cc=deeratho@cisco.com \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.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