From: syzbot <syzbot+473d7477c523b41d4046@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Forwarded: [PATCH] tty: protect break handling against disconnect
Date: Wed, 02 Sep 2026 20:42:18 -0700 [thread overview]
Message-ID: <6a98ec9a.e7659fcc.146146.0001.GAE@google.com> (raw)
In-Reply-To: <6a9087a4.4d659fcc.734b4.0013.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: [PATCH] tty: protect break handling against disconnect
Author: adrianox@gmail.com
#syz test
Both a timed break (TCSBRK/TCSBRKP) and the unconditional TIOCSBRK/
TIOCCBRK break_ctl() calls can race against hangup and be issued for a
tty whose driver data is gone, causing a use-after-free or NULL-pointer
dereference in the driver.
Check the tty hung-up state before every break_ctl() call in the tty
core, and return -ENODEV in serial_break() once the device is no longer
attached, like serial_write() already does.
---
drivers/tty/tty_io.c | 19 +++++++++++++++----
drivers/usb/serial/usb-serial.c | 3 +++
2 files changed, 18 insertions(+), 4 deletions(-)
diff --git a/drivers/tty/tty_io.c b/drivers/tty/tty_io.c
index 48569035da56..272f2839acdb 100644
--- a/drivers/tty/tty_io.c
+++ b/drivers/tty/tty_io.c
@@ -2429,6 +2429,7 @@ static int tiocgetd(struct tty_struct *tty, int __user *p)
/**
* send_break - performed time break
+ * @file: file object
* @tty: device to break on
* @duration: timeout in mS
*
@@ -2438,13 +2439,16 @@ static int tiocgetd(struct tty_struct *tty, int __user *p)
* Locking:
* @tty->atomic_write_lock serializes
*/
-static int send_break(struct tty_struct *tty, unsigned int duration)
+static int send_break(struct file *file, struct tty_struct *tty, unsigned int duration)
{
int retval;
if (tty->ops->break_ctl == NULL)
return 0;
+ if (tty_hung_up_p(file))
+ return -EIO;
+
if (tty->driver->flags & TTY_DRIVER_HARDWARE_BREAK)
return tty->ops->break_ctl(tty, duration);
@@ -2455,7 +2459,10 @@ static int send_break(struct tty_struct *tty, unsigned int duration)
retval = tty->ops->break_ctl(tty, -1);
if (!retval) {
msleep_interruptible(duration);
- retval = tty->ops->break_ctl(tty, 0);
+ if (tty_hung_up_p(file))
+ retval = -EIO;
+ else
+ retval = tty->ops->break_ctl(tty, 0);
} else if (retval == -EOPNOTSUPP) {
/* some drivers can tell only dynamically */
retval = 0;
@@ -2714,10 +2721,14 @@ long tty_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
* Break handling
*/
case TIOCSBRK: /* Turn break on, unconditionally */
+ if (tty_hung_up_p(file))
+ return -EIO;
if (tty->ops->break_ctl)
return tty->ops->break_ctl(tty, -1);
return 0;
case TIOCCBRK: /* Turn break off, unconditionally */
+ if (tty_hung_up_p(file))
+ return -EIO;
if (tty->ops->break_ctl)
return tty->ops->break_ctl(tty, 0);
return 0;
@@ -2727,10 +2738,10 @@ long tty_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
* This is used by the tcdrain() termios function.
*/
if (!arg)
- return send_break(tty, 250);
+ return send_break(file, tty, 250);
return 0;
case TCSBRKP: /* support for POSIX tcsendbreak() */
- return send_break(tty, arg ? arg*100 : 250);
+ return send_break(file, tty, arg ? arg * 100 : 250);
case TIOCMGET:
return tty_tiocmget(tty, p);
diff --git a/drivers/usb/serial/usb-serial.c b/drivers/usb/serial/usb-serial.c
index 17edc057a311..5f42bfe39212 100644
--- a/drivers/usb/serial/usb-serial.c
+++ b/drivers/usb/serial/usb-serial.c
@@ -532,6 +532,9 @@ static int serial_break(struct tty_struct *tty, int break_state)
{
struct usb_serial_port *port = tty->driver_data;
+ if (port->serial->dev->state == USB_STATE_NOTATTACHED)
+ return -ENODEV;
+
dev_dbg(&port->dev, "%s\n", __func__);
if (port->serial->type->break_ctl)
--
2.51.0
next prev parent reply other threads:[~2026-09-03 3:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 18:53 [syzbot] [usb?] general protection fault in keyspan_break_ctl syzbot
2026-08-28 1:28 ` Forwarded: [PATCH] usb: serial: keyspan: add debug prints to trace NULL p_priv syzbot
2026-08-28 6:53 ` [syzbot] [usb?] general protection fault in keyspan_break_ctl Johan Hovold
2026-09-03 2:25 ` Forwarded: [PATCH] tty: fix break race syzbot
2026-09-03 3:25 ` Forwarded: syzbot
2026-09-03 3:42 ` syzbot [this message]
2026-09-03 14:55 ` [syzbot] [usb?] general protection fault in keyspan_break_ctl syzbot
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=6a98ec9a.e7659fcc.146146.0001.GAE@google.com \
--to=syzbot+473d7477c523b41d4046@syzkaller.appspotmail.com \
--cc=linux-kernel@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®