From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Hui Peng <benquike@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
linux-serial <linux-serial@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH v4 3/3] serial: core: reject baud_base values that overflow port->uartclk in uart_set_info()
Date: Thu, 24 Sep 2026 14:40:29 +0300 (EEST) [thread overview]
Message-ID: <5e819651-e077-d7a1-d950-752e3320a436@linux.intel.com> (raw)
In-Reply-To: <20260924065510.2587569-1-benquike@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2847 bytes --]
On Thu, 24 Sep 2026, Hui Peng 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).
>
> Reject new_info->baud_base > UINT_MAX / 16 before multiplying by 16 in
> uart_set_info().
>
> 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")
> Fixes: 6eabce6608d6 ("serial: core: check uartclk for zero to avoid divide by zero")
> Cc: stable@vger.kernel.org
> Assisted-by: LLM
> Signed-off-by: Hui Peng <benquike@gmail.com>
> ---
> Changes in v4:
> - Check new_info->baud_base > UINT_MAX / 16 before multiplying by 16,
> as suggested by Ilpo Järvinen.
>
> Changes in v3:
> - Add missing #include <linux/limits.h> for UINT_MAX and move the
> new_info->baud_base > UINT_MAX / 16 check to the uartclk == 0 check, as
> suggested by Ilpo Järvinen.
>
> drivers/tty/serial/serial_core.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/tty/serial/serial_core.c b/drivers/tty/serial/serial_core.c
> index 95774b0f1484..75bb1eaa27e7 100644
> --- a/drivers/tty/serial/serial_core.c
> +++ b/drivers/tty/serial/serial_core.c
> @@ -16,6 +16,7 @@
> #include <linux/console.h>
> #include <linux/gpio/consumer.h>
> #include <linux/kernel.h>
> +#include <linux/limits.h>
> #include <linux/of.h>
> #include <linux/pm_runtime.h>
> #include <linux/proc_fs.h>
> @@ -931,8 +932,13 @@ 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;
> + unsigned int uartclk;
> +
> /* check needs to be done here before other settings made */
> + if (new_info->baud_base > UINT_MAX / 16)
> + return -EINVAL;
> +
> + uartclk = new_info->baud_base * 16;
> if (uartclk == 0)
> return -EINVAL;
> }
>
Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
--
i.
prev parent reply other threads:[~2026-09-24 11:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 6:04 [PATCH v4 0/3] serial: fix IRQ chain race, baud fallback, and uartclk overflow Hui Peng
2026-09-24 6:04 ` [PATCH v4 1/3] serial: 8250: hold hash_mutex across IRQ chain linking in serial_link_irq_chain() Hui Peng
2026-09-24 6:04 ` [PATCH v4 2/3] serial: core: allow third iteration in uart_get_baud_rate() fallback Hui Peng
2026-09-24 12:29 ` Andy Shevchenko
2026-09-24 6:42 ` [PATCH v4 0/3] serial: fix IRQ chain race, baud fallback, and uartclk overflow Greg KH
2026-09-24 6:54 ` [PATCH v4 3/3] serial: core: reject baud_base values that overflow port->uartclk in uart_set_info() Hui Peng
2026-09-24 11:40 ` Ilpo Järvinen [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=5e819651-e077-d7a1-d950-752e3320a436@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=benquike@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--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®