From: Ruben Wauters <rubenru09@aol.com>
To: Deepanshu Kartikey <kartikey406@gmail.com>,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch
Cc: peter@stuge.se, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
syzbot+916c888ba5f1a54c9526@syzkaller.appspotmail.com
Subject: Re: [PATCH] drm/gud: NUL-terminate TV mode names read from the device
Date: Sun, 23 Aug 2026 16:41:26 +0100 [thread overview]
Message-ID: <6c3a749f8d377b122ba33fd06825d8faff345006.camel@aol.com> (raw)
In-Reply-To: <2973ae0d1d7ca4c39ef2cb07236ace25d400fdd0.camel@aol.com>
[-- Attachment #1: Type: text/plain, Size: 2025 bytes --]
On Mon, 2026-08-17 at 16:36 +0100, Ruben Wauters wrote:
> On Sun, 2026-08-16 at 14:22 +0530, Deepanshu Kartikey wrote:
> > gud_connector_add_tv_mode() reads a buffer of fixed-size mode names from
> > the USB device and passes pointers into it to
> > drm_mode_create_tv_properties_legacy(), which calls strlen() on each one.
> > Nothing guarantees the device NUL-terminates a name, so strlen() can run
> > past the end of a slot and, for the last mode, past the end of the
> > allocation.
> >
> > Terminate each name at the end of its slot before use.
> >
> > Fixes: 40e1a70b4aed ("drm: Add GUD USB Display driver")
> > Reported-by: syzbot+916c888ba5f1a54c9526@syzkaller.appspotmail.com
> > Closes: https://syzkaller.appspot.com/bug?extid=916c888ba5f1a54c9526
> > Tested-by: syzbot+916c888ba5f1a54c9526@syzkaller.appspotmail.com
> > Signed-off-by: Deepanshu Kartikey <kartikey406@gmail.com>
> Acked-by: Ruben Wauters <rubenru09@aol.com>
Thank you, applied to drm-misc-fixes, Cc'd stable
Ruben
> > ---
> > drivers/gpu/drm/gud/gud_connector.c | 9 +++++++--
> > 1 file changed, 7 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/gud/gud_connector.c b/drivers/gpu/drm/gud/gud_connector.c
> > index ea0cca58b7c8..5c0065c876a7 100644
> > --- a/drivers/gpu/drm/gud/gud_connector.c
> > +++ b/drivers/gpu/drm/gud/gud_connector.c
> > @@ -396,8 +396,13 @@ static int gud_connector_add_tv_mode(struct gud_device *gdrm, struct drm_connect
> > }
> >
> > num_modes = ret / GUD_CONNECTOR_TV_MODE_NAME_LEN;
> > - for (i = 0; i < num_modes; i++)
> > - modes[i] = &buf[i * GUD_CONNECTOR_TV_MODE_NAME_LEN];
> > + for (i = 0; i < num_modes; i++) {
> > + char *mode = &buf[i * GUD_CONNECTOR_TV_MODE_NAME_LEN];
> > +
> > + /* The device is not trusted to NUL-terminate the name */
> > + mode[GUD_CONNECTOR_TV_MODE_NAME_LEN - 1] = '\0';
> > + modes[i] = mode;
> > + }
> >
> > ret = drm_mode_create_tv_properties_legacy(connector->dev, num_modes, modes);
> > free:
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 870 bytes --]
next prev parent reply other threads:[~2026-08-23 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 8:52 Deepanshu Kartikey
[not found] ` <20260816090040.68D5B1F000E9@smtp.kernel.org>
2026-08-17 15:36 ` Ruben Wauters
2026-08-17 15:36 ` Ruben Wauters
2026-08-23 15:41 ` Ruben Wauters [this message]
2026-08-23 15:59 ` Ruben Wauters
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=6c3a749f8d377b122ba33fd06825d8faff345006.camel@aol.com \
--to=rubenru09@aol.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=peter@stuge.se \
--cc=simona@ffwll.ch \
--cc=syzbot+916c888ba5f1a54c9526@syzkaller.appspotmail.com \
--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®