From: Hugo Villeneuve <hugo@hugovil.com>
To: Hui Peng <benquike@gmail.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"John Ogness" <john.ogness@linutronix.de>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v8 2/2] serial: core: reject baud_base values that overflow port->uartclk in uart_set_info()
Date: Thu, 15 Oct 2026 11:34:22 -0400 [thread overview]
Message-ID: <20261015113422.007d26d4c5135aa6a3add4a4@hugovil.com> (raw)
In-Reply-To: <20261007094719.1362769-3-benquike@gmail.com>
Hi Hui,
On Wed, 7 Oct 2026 09:47:18 +0000
Hui Peng <benquike@gmail.com> wrote:
> In uart_set_info(), new_info->baud_base is multiplied by 16 and stored in
> uport->uartclk (an unsigned int):
>
> uport->uartclk = new_info->baud_base * 16;
>
> While uart_set_info() checks if (uartclk == 0) and
> if (new_info->baud_base < 9600), when new_info->baud_base exceeds
> UINT_MAX / 16 with low bits set (for example, 0x10000001), multiplying
> by 16 wraps around in 32-bit unsigned arithmetic to a small non-zero value
> (16), bypassing both uartclk == 0 and new_info->baud_base < 9600 and
> setting uport->uartclk = 16 (baud_base = 1, well below the required
> minimum of 9600 * 16).
>
> Use check_mul_overflow(new_info->baud_base, 16, &uartclk) in
> uart_set_info() to reject overflowing baud_base values with -EINVAL.
>
> Tested in QEMU against Linux 7.3.0-rc3 by calling ioctl(fd, TIOCSSERIAL,
> &ss) with ss.baud_base = 0x10000001 on /dev/ttyS1: on the unfixed kernel
> TIOCSSERIAL succeeds (ret = 0) and wraps uport->uartclk to 16
> (TIOCGSERIAL reports baud_base = 1), whereas with the fix applied
> TIOCSSERIAL returns -EINVAL and preserves the existing uport->uartclk.
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Cc: stable@vger.kernel.org
> Assisted-by: LLM
> Signed-off-by: Hui Peng <benquike@gmail.com>
> ---
> Changes in v8:
> - Dropped secondary Fixes: 6eabce6608d6 tag per Hugo Villeneuve feedback.
>
> Changes in v7:
> - Use check_mul_overflow() instead of raw UINT_MAX / 16 comparison as
> suggested by Jiri Slaby.
>
> drivers/tty/serial/serial_core.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/tty/serial/serial_core.c b/drivers/tty/serial/serial_core.c
> index 6ed0195e6912..9a8f4c2e1180 100644
> --- a/drivers/tty/serial/serial_core.c
> +++ b/drivers/tty/serial/serial_core.c
> @@ -14,6 +14,7 @@
> #include <linux/tty_flip.h>
> #include <linux/serial_core.h>
> #include <linux/console.h>
> +#include <linux/overflow.h>
> #include <linux/gpio/consumer.h>
> #include <linux/kernel.h>
> #include <linux/of.h>
> @@ -931,9 +932,11 @@ static int uart_set_info(struct tty_struct *tty, struct tty_port *port,
> old_custom_divisor = uport->custom_divisor;
>
> if (!(uport->flags & UPF_FIXED_PORT)) {
> - unsigned int uartclk = new_info->baud_base * 16;
>
> /* check needs to be done here before other settings made */
> - if (uartclk == 0)
> + unsigned int uartclk;
If you leave uartclk declaration before the comments, the diff will be
simpler.
> +
> + if (check_mul_overflow(new_info->baud_base, 16, &uartclk) ||
> + uartclk == 0)
> return -EINVAL;
> }
> --
> 2.47.3
>
--
Hugo Villeneuve
prev parent reply other threads:[~2026-10-15 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 9:47 [PATCH v8 0/2] serial: core: fix baud rate fallback loop and baud_base overflow Hui Peng
2026-10-07 9:47 ` [PATCH v8 1/2] serial: core: fix baud rate fallback in uart_get_baud_rate() Hui Peng
2026-10-07 10:43 ` Ilpo Järvinen
2026-10-07 14:13 ` Hugo Villeneuve
2026-10-07 9:47 ` [PATCH v8 2/2] serial: core: reject baud_base values that overflow port->uartclk in uart_set_info() Hui Peng
2026-10-15 15:34 ` Hugo Villeneuve [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=20261015113422.007d26d4c5135aa6a3add4a4@hugovil.com \
--to=hugo@hugovil.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=benquike@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=stable@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 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®