From: Thomas Zimmermann <tzimmermann@suse.de>
To: Javier Martinez Canillas <javierm@redhat.com>,
linux-kernel@vger.kernel.org
Cc: linux-fbdev@vger.kernel.org,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Helge Deller <deller@gmx.de>,
dri-devel@lists.freedesktop.org, Peter Jones <pjones@redhat.com>
Subject: Re: [PATCH 3/3] fbdev/efifb: Cleanup fb_info in .fb_destroy rather than .remove
Date: Thu, 5 May 2022 09:30:53 +0200 [thread overview]
Message-ID: <b82329d5-19af-77b5-ea7d-757b95959ab6@suse.de> (raw)
In-Reply-To: <20220504215806.57147-1-javierm@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 2356 bytes --]
Am 04.05.22 um 23:58 schrieb Javier Martinez Canillas:
> The driver is calling framebuffer_release() in its .remove callback, but
> this will cause the struct fb_info to be freed too early. Since it could
> be that a reference is still hold to it if user-space opened the fbdev.
>
> This would lead to a use-after-free error if the framebuffer device was
> unregistered but later a user-space process tries to close the fbdev fd.
>
> The correct thing to do is to only unregister the framebuffer in the
> driver's .remove callback, but do any cleanup in the fb_ops.fb_destroy.
>
> Suggested-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
> ---
>
> drivers/video/fbdev/efifb.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/video/fbdev/efifb.c b/drivers/video/fbdev/efifb.c
> index ea42ba6445b2..cfa3dc0b4eee 100644
> --- a/drivers/video/fbdev/efifb.c
> +++ b/drivers/video/fbdev/efifb.c
> @@ -243,6 +243,10 @@ static void efifb_show_boot_graphics(struct fb_info *info)
> static inline void efifb_show_boot_graphics(struct fb_info *info) {}
> #endif
>
> +/*
> + * fb_ops.fb_destroy is called by the last put_fb_info() call at the end
> + * of unregister_framebuffer() or fb_release(). Do any cleanup here.
> + */
> static void efifb_destroy(struct fb_info *info)
> {
> if (efifb_pci_dev)
> @@ -254,6 +258,9 @@ static void efifb_destroy(struct fb_info *info)
> else
> memunmap(info->screen_base);
> }
> +
> + framebuffer_release(info);
> +
> if (request_mem_succeeded)
> release_mem_region(info->apertures->ranges[0].base,
> info->apertures->ranges[0].size);
> @@ -620,9 +627,9 @@ static int efifb_remove(struct platform_device *pdev)
> {
> struct fb_info *info = platform_get_drvdata(pdev);
>
> + /* efifb_destroy takes care of info cleanup */
> unregister_framebuffer(info);
> sysfs_remove_groups(&pdev->dev.kobj, efifb_groups);
> - framebuffer_release(info);
>
> return 0;
> }
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-05-05 7:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 21:51 [PATCH 0/3] fbdev: Fix use-after-free caused by wrong fb_info cleanup in drivers Javier Martinez Canillas
2022-05-04 21:56 ` [PATCH 1/3] fbdev: Prevent possible use-after-free in fb_release() Javier Martinez Canillas
2022-05-05 7:31 ` Thomas Zimmermann
2022-05-04 21:57 ` [PATCH 2/3] fbdev/simplefb: Cleanup fb_info in .fb_destroy rather than .remove Javier Martinez Canillas
2022-05-05 7:29 ` Thomas Zimmermann
2022-05-05 7:38 ` Javier Martinez Canillas
2022-05-05 8:05 ` Thomas Zimmermann
2022-05-05 8:28 ` Javier Martinez Canillas
2022-05-05 8:49 ` Thomas Zimmermann
2022-05-05 12:57 ` Daniel Vetter
2022-05-05 12:52 ` Daniel Vetter
2022-05-05 12:57 ` Javier Martinez Canillas
2022-05-04 21:58 ` [PATCH 3/3] fbdev/efifb: " Javier Martinez Canillas
2022-05-05 7:30 ` Thomas Zimmermann [this message]
2022-05-05 8:16 ` [PATCH 0/3] fbdev: Fix use-after-free caused by wrong fb_info cleanup in drivers Thomas Zimmermann
2022-05-05 8:30 ` Javier Martinez Canillas
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=b82329d5-19af-77b5-ea7d-757b95959ab6@suse.de \
--to=tzimmermann@suse.de \
--cc=daniel.vetter@ffwll.ch \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pjones@redhat.com \
/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®