mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Tuo Li <islituo@gmail.com>,
	simona@ffwll.ch, kees@kernel.org, tzimmermann@suse.de
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fbdev:modedb: fix a possible UAF in fb_find_mode()
Date: Sun, 7 Jun 2026 18:12:05 +0200	[thread overview]
Message-ID: <2d96dd04-855f-45d6-8bf1-7b6704181397@gmx.de> (raw)
In-Reply-To: <20260526091507.421730-1-islituo@gmail.com>

On 5/26/26 11:15, Tuo Li wrote:
> If mode_option is NULL, it is assigned from mode_option_buf:
> 
>    if (!mode_option) {
>      fb_get_options(NULL, &mode_option_buf);
>      mode_option = mode_option_buf;
>    }
> 
> Later, name is assigned from mode_option:
> 
>    const char *name = mode_option;
> 
> However, mode_option_buf is freed before name is no longer used:
> 
>    kfree(mode_option_buf);
> 
> while name is still accessed by:
> 
>    if ((name_matches(db[i], name, namelen) ||
> 
> Since name aliases mode_option_buf, this may result in a
> use-after-free.
> 
> Fix this by moving the kfree(mode_option_buf) call behind the access, and
> add corresponding cleanup before early returns.

I wonder if this isn't a typical good use-case for the new "Scope-based
resource management for the kernel" [1] feature.

Instead of adding kfree() at various places, we could do:

diff --git a/drivers/video/fbdev/core/modedb.c b/drivers/video/fbdev/core/modedb.c
index 703d0b7aec32..b6926764a99c 100644
--- a/drivers/video/fbdev/core/modedb.c
+++ b/drivers/video/fbdev/core/modedb.c
@@ -626,7 +626,7 @@ int fb_find_mode(struct fb_var_screeninfo *var,
                  const struct fb_videomode *default_mode,
                  unsigned int default_bpp)
  {
-       char *mode_option_buf = NULL;
+       char *mode_option_buf __free(kfree) = NULL;
         int i;
  
         /* Set up defaults */
@@ -724,7 +724,6 @@ int fb_find_mode(struct fb_var_screeninfo *var,
                         res_specified = 1;
                 }
  done:
-               kfree(mode_option_buf);
                 if (cvt) {
                         struct fb_videomode cvt_mode;
                         int ret;


[1] https://lwn.net/Articles/934679/


Do you want to check if that's correct, and if yes resend a patch?

Helge

  reply	other threads:[~2026-06-07 16:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26  9:15 Tuo Li
2026-06-07 16:12 ` Helge Deller [this message]
2026-06-10  2:21   ` Tuo Li

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=2d96dd04-855f-45d6-8bf1-7b6704181397@gmx.de \
    --to=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=islituo@gmail.com \
    --cc=kees@kernel.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.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®