From: Helge Deller <deller@gmx.de>
To: Li Ximo <lixicaicai@gmail.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Wang Haoran <haoranwangsec@gmail.com>
Subject: Re: [PATCH] video: fbdev: atmel_lcdfb: fix list_first_entry() on possibly empty modelist in probe
Date: Sun, 25 Oct 2026 08:57:02 +0100 [thread overview]
Message-ID: <951c65be-d4bb-4177-8106-67a72960fba6@gmx.de> (raw)
In-Reply-To: <20261023075611.3559095-1-lixicaicai@gmail.com>
On 10/23/26 09:56, Li Ximo wrote:
> From: Wang Haoran <haoranwangsec@gmail.com>
>
> list_first_entry() does not return NULL on an empty list; it returns a
> bogus pointer computed by container_of() from the list head.
> atmel_lcdfb_probe() initializes info->modelist with INIT_LIST_HEAD()
> and later takes its first entry with list_first_entry(), assuming
> atmel_lcdfb_of_init() populated it. However, atmel_lcdfb_of_init()
> drops the return value of fb_add_videomode() — unlike every other
> fallible call in the same function — so if fb_add_videomode() fails
> (its internal kmalloc can return -ENOMEM under memory pressure or
> fault injection), the list stays empty while of_init() reports
> success. The probe path then dereferences the bogus pointer in
> fb_videomode_to_var(&info->var, &modelist->mode). Because the bogus
> pointer lands inside the contiguous fb_info allocation, this may not
> fault immediately; instead it silently reads adjacent memory as a
> struct fb_videomode and programs garbage timing parameters into the
> LCD controller. This was found by code audit; we do not have Atmel
> hardware to reproduce it.
>
> Fix this on two levels: check the return value of fb_add_videomode()
> in atmel_lcdfb_of_init() so the failure is propagated (root cause),
> and use list_first_entry_or_null() in atmel_lcdfb_probe() with a NULL
> check that fails probe gracefully with -EINVAL (defense in depth),
> consistent with the surrounding error handling which bails out to
> stop_clk.
>
> Reported-by: Wang Haoran <haoranwangsec@gmail.com>
> Reported-by: Li Ximo <lixicaicai@gmail.com>
> Signed-off-by: Wang Haoran <haoranwangsec@gmail.com>
> ---
> drivers/video/fbdev/atmel_lcdfb.c | 13 ++++++++++---
> 1 file changed, 10 insertions(+), 3 deletions(-)
applied.
Thanks!
Helge
prev parent reply other threads:[~2026-10-25 7:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 7:56 [PATCH] video: fbdev: atmel_lcdfb: fix list_first_entry() on possibly empty modelist in probe Li Ximo
2026-10-25 7:57 ` 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=951c65be-d4bb-4177-8106-67a72960fba6@gmx.de \
--to=deller@gmx.de \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=dri-devel@lists.freedesktop.org \
--cc=haoranwangsec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixicaicai@gmail.com \
--cc=nicolas.ferre@microchip.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