From: Baruch Siach <baruch@tkos.co.il>
To: Junrui Luo <moonafterrain@outlook.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Yuhao Jiang <danisjiang@gmail.com>
Subject: Re: [PATCH] serial: digicolor: fix use-after-free on driver unbind
Date: Mon, 22 Dec 2025 07:41:46 +0200 [thread overview]
Message-ID: <871pkndqed.fsf@tarshish> (raw)
In-Reply-To: <SYBPR01MB7881327BF7F679E76A7315DEAFB4A@SYBPR01MB7881.ausprd01.prod.outlook.com> (Junrui Luo's message of "Mon, 22 Dec 2025 12:55:02 +0800")
Hi Junrui,
On Mon, Dec 22 2025, Junrui Luo wrote:
> The digicolor_uart_console_write() function accesses the global
> digicolor_ports[] array to retrieve the uart port pointer, which
> can lead to a use-after-free if the console write occurs after
> the port has been removed via unbind.
>
> digicolor_uart_remove() leaves a dangling pointer in the array.
>
> Fix by clearing the array entry in digicolor_uart_remove() and
> adding a NULL check in digicolor_uart_console_write().
Thanks for the patch.
Is this .write/.remove callbacks race actually possible? Can you refer
me to similar fixes in other drivers?
> Reported-by: Yuhao Jiang <danisjiang@gmail.com>
Where can I find this report?
Thanks,
baruch
> Reported-by: Junrui Luo <moonafterrain@outlook.com>
> Fixes: 5930cb3511df ("serial: driver for Conexant Digicolor USART")
> Signed-off-by: Junrui Luo <moonafterrain@outlook.com>
> ---
> drivers/tty/serial/digicolor-usart.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/tty/serial/digicolor-usart.c b/drivers/tty/serial/digicolor-usart.c
> index d2482df5cb9b..5861be2072c4 100644
> --- a/drivers/tty/serial/digicolor-usart.c
> +++ b/drivers/tty/serial/digicolor-usart.c
> @@ -397,6 +397,9 @@ static void digicolor_uart_console_write(struct console *co, const char *c,
> unsigned long flags;
> int locked = 1;
>
> + if (!port)
> + return;
> +
> if (oops_in_progress)
> locked = uart_port_trylock_irqsave(port, &flags);
> else
> @@ -508,6 +511,7 @@ static void digicolor_uart_remove(struct platform_device *pdev)
> struct uart_port *port = platform_get_drvdata(pdev);
>
> uart_remove_one_port(&digicolor_uart, port);
> + digicolor_ports[port->line] = NULL;
> }
>
> static const struct of_device_id digicolor_uart_dt_ids[] = {
>
> ---
> base-commit: ea1013c1539270e372fc99854bc6e4d94eaeff66
> change-id: 20251222-fixes-74e6b26513d1
>
> Best regards,
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2025-12-22 5:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 4:55 [PATCH] serial: digicolor: fix use-after-free on driver unbind Junrui Luo
2025-12-22 5:41 ` Baruch Siach [this message]
2025-12-22 6:22 ` Greg Kroah-Hartman
2025-12-25 4:23 ` Junrui Luo
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=871pkndqed.fsf@tarshish \
--to=baruch@tkos.co.il \
--cc=danisjiang@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=moonafterrain@outlook.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 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.