From: Markus Probst <markus.probst@posteo.de>
To: Hans de Goede <johannes.goede@oss.qualcomm.com>,
Rob Herring <robh@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>
Cc: Ibrahim Abdelkader <iabdelka@qti.qualcomm.com>,
linux-bluetooth@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH] serdev: ttyport: Clear serport->tty after freeing
Date: Wed, 19 Aug 2026 16:44:12 +0000 [thread overview]
Message-ID: <e9e7a52f8d11ec8f57a72424bfaa40eaf738f1e9.camel@posteo.de> (raw)
In-Reply-To: <20260819125748.194377-1-johannes.goede@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 2419 bytes --]
On Wed, 2026-08-19 at 14:57 +0200, Hans de Goede wrote:
> From: Ibrahim Abdelkader <iabdelka@qti.qualcomm.com>
>
> Both error paths in ttyport_open(), and ttyport_close(), release the tty
> with tty_release_struct() and leave serport->tty pointing at freed memory.
>
> The serdev core itself never dereferences it afterwards. However, a buggy
> driver could easily trigger a use-after-free by calling a ttyport operation
> on a port that is not open, or by calling close() twice. While those
> drivers should be fixed, clearing the pointer, makes them fail
> deterministically instead of touching freed memory.
>
> Note that a driver which currently double closes gets away with it only by
> chance, depending on whether the freed tty has been reused. After this
> change such a driver oopses immediately instead, which is the intended
> outcome, but it may surface latent bugs elsewhere.
>
> Signed-off-by: Ibrahim Abdelkader <iabdelka@qti.qualcomm.com>
> Reviewed-by: Hans de Goede <johannes.goede@oss.qualcomm.com>
> Signed-off-by: Hans de Goede <johannes.goede@oss.qualcomm.com>
I recently took the role as maintainer for serdev [1].
Please add me to CC if sending another revision.
I only look loosly at the linux-serial mailing list, so I might
otherwise miss a patch.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core.git/commit/MAINTAINERS?h=driver-core-next&id=6b71fef6f05cee64ebbaa8aec6dc688169f47e9c
> ---
> drivers/tty/serdev/serdev-ttyport.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/tty/serdev/serdev-ttyport.c b/drivers/tty/serdev/serdev-ttyport.c
> index bab1b143b8a6..b6638f9f40d2 100644
> --- a/drivers/tty/serdev/serdev-ttyport.c
> +++ b/drivers/tty/serdev/serdev-ttyport.c
> @@ -137,6 +137,7 @@ static int ttyport_open(struct serdev_controller *ctrl)
> err_unlock:
> tty_unlock(tty);
> tty_release_struct(tty, serport->tty_idx);
> + serport->tty = NULL;
>
> return ret;
> }
> @@ -154,6 +155,7 @@ static void ttyport_close(struct serdev_controller *ctrl)
> tty_unlock(tty);
>
> tty_release_struct(tty, serport->tty_idx);
> + serport->tty = NULL;
> }
>
> static unsigned int ttyport_set_baudrate(struct serdev_controller *ctrl, unsigned int speed)
Always good to see hardening.
Reviewed-by: Markus Probst <markus.probst@posteo.de>
Thanks
- Markus Probst
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 870 bytes --]
prev parent reply other threads:[~2026-08-19 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 12:57 [PATCH] serdev: ttyport: Clear serport->tty after freeing Hans de Goede
2026-08-19 13:53 ` bluez.test.bot
2026-08-19 16:44 ` Markus Probst [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=e9e7a52f8d11ec8f57a72424bfaa40eaf738f1e9.camel@posteo.de \
--to=markus.probst@posteo.de \
--cc=gregkh@linuxfoundation.org \
--cc=iabdelka@qti.qualcomm.com \
--cc=jirislaby@kernel.org \
--cc=johannes.goede@oss.qualcomm.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh@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