The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Murad Masimov <m.masimov@mt-integration.ru>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, lvc-project@linuxtesting.org
Subject: Re: [PATCH 0/2] fbdev: Prevent null-ptr-deref in fb_videomode_to_var
Date: Thu, 29 May 2025 10:19:11 +0200	[thread overview]
Message-ID: <62fff638-0898-4952-b159-d4c8a13e6d24@gmx.de> (raw)
In-Reply-To: <20250428153407.3743416-1-m.masimov@mt-integration.ru>

On 4/28/25 17:34, Murad Masimov wrote:
> These patches fix the bug that leads to a null-ptr-deref if
> fb_videomode_to_var() fails to allocate memory. This bug is present in
> do_register_framebuffer() and fb_ser_var().
> 
> Found by Linux Verification Center (linuxtesting.org) with Syzkaller.
> 
> Murad Masimov (2):
>    fbdev: Fix do_register_framebuffer to prevent null-ptr-deref in
>      fb_videomode_to_var
>    fbdev: Fix fb_ser_var to prevent null-ptr-deref in fb_videomode_to_var

I've added both patches to fbdev git tree (after fixing two small typos in commit message).

Thanks!
Helge



  
>   drivers/video/fbdev/core/fbmem.c | 22 ++++++++++++++--------
>   1 file changed, 14 insertions(+), 8 deletions(-)
> 
> --
> 2.39.2
> 


      parent reply	other threads:[~2025-05-29  8:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-28 15:34 [PATCH 0/2] fbdev: Prevent null-ptr-deref in fb_videomode_to_var Murad Masimov
2025-04-28 15:34 ` [PATCH 1/2] fbdev: Fix do_register_framebuffer to prevent " Murad Masimov
2025-04-28 15:34 ` [PATCH 2/2] fbdev: Fix fb_ser_var " Murad Masimov
2025-05-29  8:19 ` 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=62fff638-0898-4952-b159-d4c8a13e6d24@gmx.de \
    --to=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lvc-project@linuxtesting.org \
    --cc=m.masimov@mt-integration.ru \
    /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