From: lyude@redhat.com
To: Ashutosh Desai <ashutoshdesai993@gmail.com>,
dri-devel@lists.freedesktop.org
Cc: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/dp/mst: fix OOB reads on 2-byte fields in sideband reply parsers
Date: Thu, 07 May 2026 15:22:04 -0400 [thread overview]
Message-ID: <3af593e5ff0c3afa7e9e10b06ed9b6c9ab9edad2.camel@redhat.com> (raw)
In-Reply-To: <20260410040026.2436280-1-ashutoshdesai993@gmail.com>
Comments down below
On Fri, 2026-04-10 at 04:00 +0000, Ashutosh Desai wrote:
> Three sideband reply parsers read 16-bit fields as:
>
> val = (raw->msg[idx] << 8) | (raw->msg[idx+1]);
>
> and only check bounds after the fact (idx += 2, then
> if (idx > raw->curlen)). When idx == raw->curlen at the
> point of the read, raw->msg[idx+1] is one byte past the
> received message data, reading into the following struct
> fields (curchunk_len, curchunk_idx, curlen).
>
> Affected functions:
> - drm_dp_sideband_parse_enum_path_resources_ack()
> full_payload_bw_number and avail_payload_bw_number fields
> - drm_dp_sideband_parse_allocate_payload_ack()
> allocated_pbn field
> - drm_dp_sideband_parse_query_payload_ack()
> allocated_pbn field
>
> Move the bounds check to immediately before each 2-byte read,
> using idx + 2 > raw->curlen, consistent with the fix pattern
> used elsewhere in this file.
>
> Signed-off-by: Ashutosh Desai <ashutoshdesai993@gmail.com>
> ---
> drivers/gpu/drm/display/drm_dp_mst_topology.c | 17 +++++++----------
> 1 file changed, 7 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/gpu/drm/display/drm_dp_mst_topology.c
> b/drivers/gpu/drm/display/drm_dp_mst_topology.c
> index 9cef6c576..f2a7dbc5e 100644
> --- a/drivers/gpu/drm/display/drm_dp_mst_topology.c
> +++ b/drivers/gpu/drm/display/drm_dp_mst_topology.c
> @@ -931,14 +931,13 @@ static bool
> drm_dp_sideband_parse_enum_path_resources_ack(struct drm_dp_sideband
> idx++;
> if (idx > raw->curlen)
> goto fail_len;
> + if (idx + 2 > raw->curlen)
> + goto fail_len;
Same feedback as the other patch - we can just remove the idx check
above and replace it with the idx + 2 > raw->curlen check.
> repmsg->u.path_resources.full_payload_bw_number = (raw-
> >msg[idx] << 8) | (raw->msg[idx+1]);
> idx += 2;
> - if (idx > raw->curlen)
> + if (idx + 2 > raw->curlen)
> goto fail_len;
> repmsg->u.path_resources.avail_payload_bw_number = (raw-
> >msg[idx] << 8) | (raw->msg[idx+1]);
> - idx += 2;
> - if (idx > raw->curlen)
> - goto fail_len;
> return true;
> fail_len:
> DRM_DEBUG_KMS("enum resource parse length fail %d %d\n",
> idx, raw->curlen);
> @@ -958,10 +957,9 @@ static bool
> drm_dp_sideband_parse_allocate_payload_ack(struct drm_dp_sideband_ms
> idx++;
> if (idx > raw->curlen)
> goto fail_len;
> - repmsg->u.allocate_payload.allocated_pbn = (raw->msg[idx] <<
> 8) | (raw->msg[idx+1]);
> - idx += 2;
> - if (idx > raw->curlen)
> + if (idx + 2 > raw->curlen)
> goto fail_len;
> + repmsg->u.allocate_payload.allocated_pbn = (raw->msg[idx] <<
> 8) | (raw->msg[idx+1]);
> return true;
> fail_len:
> DRM_DEBUG_KMS("allocate payload parse length fail %d %d\n",
> idx, raw->curlen);
> @@ -977,10 +975,9 @@ static bool
> drm_dp_sideband_parse_query_payload_ack(struct drm_dp_sideband_msg_r
> idx++;
> if (idx > raw->curlen)
> goto fail_len;
> - repmsg->u.query_payload.allocated_pbn = (raw->msg[idx] << 8)
> | (raw->msg[idx + 1]);
> - idx += 2;
> - if (idx > raw->curlen)
> + if (idx + 2 > raw->curlen)
> goto fail_len;
> + repmsg->u.query_payload.allocated_pbn = (raw->msg[idx] << 8)
> | (raw->msg[idx + 1]);
> return true;
> fail_len:
> DRM_DEBUG_KMS("query payload parse length fail %d %d\n",
> idx, raw->curlen);
prev parent reply other threads:[~2026-05-07 19:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 4:00 Ashutosh Desai
2026-05-07 19:22 ` lyude [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=3af593e5ff0c3afa7e9e10b06ed9b6c9ab9edad2.camel@redhat.com \
--to=lyude@redhat.com \
--cc=airlied@gmail.com \
--cc=ashutoshdesai993@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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®