All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Weiming Shi <bestswngs@gmail.com>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, co+c25629c98ba36ebe@bugs.sh
Subject: Re: [PATCH] fbdev: vfb: defer cleanup until the last reference
Date: Thu, 10 Sep 2026 22:52:37 +0200	[thread overview]
Message-ID: <8cb3dcb1-a654-44cf-b885-8855ae7798ae@gmx.de> (raw)
In-Reply-To: <20260909191022.847295-2-bestswngs@gmail.com>

On 9/9/26 21:10, Weiming Shi wrote:
> FBIOGETCMAP takes a shallow snapshot of info->cmap and performs the
> usercopy after dropping info->lock. vfb_remove() frees the colormap
> immediately after unregistering the framebuffer, even when an open file
> still holds a reference to fb_info. A concurrent driver unbind can
> therefore free the colormap while the ioctl copies it to userspace.
> 
> KASAN reports:
> 
>    BUG: KASAN: slab-use-after-free in _copy_to_user
>    Read of size 512 by task poc/125
> 
>     _copy_to_user (./include/linux/instrumented.h:129 ./include/linux/uaccess.h:201 lib/usercopy.c:24)
>     fb_cmap_to_user (./include/linux/uaccess.h:230 drivers/video/fbdev/core/fbcmap.c:211)
>     do_fb_ioctl (drivers/video/fbdev/core/fb_chrdev.c:114)
> 
>     Allocated by task 1:
>     fb_alloc_cmap_gfp (./include/linux/slab.h:973 ./include/linux/slab.h:1290 drivers/video/fbdev/core/fbcmap.c:108)
>     vfb_probe (drivers/video/fbdev/vfb.c:459)
> 
>     Freed by task 124:
>     fb_dealloc_cmap (drivers/video/fbdev/core/fbcmap.c:151)
>     vfb_remove (drivers/video/fbdev/vfb.c:489)
> 
> unregister_framebuffer() drops the registration reference, and fbdev calls
> fb_destroy after the last put_fb_info(). Move the registered framebuffer's
> cleanup into an fb_destroy callback so its colormap and screen buffer stay
> alive until all file references have been released.
> 
> Fixes: 5e266e2e0e19 ("vfb: fix memory leaks in removal path")
> Reported-by: co+c25629c98ba36ebe@bugs.sh
> Closes: https://lore.kernel.org/linux-fbdev/f2Kf9GYn1lKR5S1dbvGVtykMxK1RlgP5z8sW@bugs.sh/
> Assisted-by: Codex:gpt-5
> Signed-off-by: Weiming Shi <bestswngs@gmail.com>
> ---
>   drivers/video/fbdev/vfb.c | 11 ++++++++---
>   1 file changed, 8 insertions(+), 3 deletions(-)
applied.

Thanks!
Helge

      parent reply	other threads:[~2026-09-10 20:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09 19:10 [PATCH] fbdev: vfb: defer cleanup until the last reference Weiming Shi
2026-09-09 19:28 ` sashiko-bot
2026-09-10 20:52 ` Helge Deller [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=8cb3dcb1-a654-44cf-b885-8855ae7798ae@gmx.de \
    --to=deller@gmx.de \
    --cc=bestswngs@gmail.com \
    --cc=co+c25629c98ba36ebe@bugs.sh \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.