From: Denis Arefev <arefev@swemel.ru>
To: stable@vger.kernel.org, Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Jiri Slaby <jirislaby@kernel.org>,
Sasha Levin <sashal@kernel.org>,
Artem Shimko <a.shimko.dev@gmail.com>,
Stepan Ionichev <sozdayvek@gmail.com>,
Serge Semin <Sergey.Semin@baikalelectronics.ru>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2 5.10] serial: 8250_dw: fix port leak on clock notifier failure
Date: Tue, 8 Sep 2026 12:36:20 +0300 [thread overview]
Message-ID: <20260908093626.15492-1-arefev@swemel.ru> (raw)
This series cleans up the error handling in dw8250_probe() and fixes a
port leak. When clk_notifier_register() fails, probe() returns an error
but the 8250 port registered just before it stays registered: the
matching serial8250_unregister_port() lives in dw8250_remove(), which is
not called on probe failure. The port slot then stays occupied until a
rebind, and the devm-allocated driver data is freed while the port still
references it (via private_data and the serial_in/serial_out callbacks),
a use-after-free hazard.
The first patch converts the probe() error paths to dev_err_probe().
The second patch unregisters the 8250 port on the
clk_notifier_register() error path.
Andy Shevchenko (1):
serial: 8250_dw: Use dev_err_probe()
Stepan Ionichev (1):
serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails
drivers/tty/serial/8250/8250_dw.c | 32 ++++++++++++++-----------------
1 file changed, 14 insertions(+), 18 deletions(-)
--
2.43.0
next reply other threads:[~2026-09-08 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 9:36 Denis Arefev [this message]
2026-09-08 9:36 ` [PATCH 1/2 5.10] serial: 8250_dw: Use dev_err_probe() Denis Arefev
2026-09-08 9:36 ` [PATCH 2/2 5.10] serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails Denis Arefev
2026-09-08 22:39 ` [PATCH 0/2 5.10] serial: 8250_dw: fix port leak on clock notifier failure Sasha Levin
2026-09-08 22:59 ` Sasha Levin
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=20260908093626.15492-1-arefev@swemel.ru \
--to=arefev@swemel.ru \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=a.shimko.dev@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=sozdayvek@gmail.com \
--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