From: Greg KH <gregkh@linuxfoundation.org>
To: Shengzhuo Wei <me@cherr.cc>
Cc: Sebastian Reichel <sre@kernel.org>,
Kai Vehmanen <kai.vehmanen@nokia.com>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Joni Lapilainen <joni.lapilainen@gmail.com>,
Carlos Chinea <carlos.chinea@nokia.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] HSI: cmt_speech: Fix crash on device removal with open file descriptor
Date: Fri, 28 Aug 2026 12:45:55 +0200 [thread overview]
Message-ID: <2026082802-plod-scroll-3acb@gregkh> (raw)
In-Reply-To: <20260828-cmt-speech-uaf-v1-1-1fed740dd225@cherr.cc>
On Fri, Aug 28, 2026 at 04:09:27PM +0800, Shengzhuo Wei wrote:
> misc_deregister() does not drain file descriptors that are already
> open, so after cs_hsi_client_remove() clears and frees
> cs_char_data.hi, the ioctl and write paths still dereference it
> without any lock or NULL check:
>
> open("/dev/cmt_speech") [userspace]
> rmmod cmt_speech [removal]
> ioctl(fd, CS_GET_STATE, 0) [userspace]
>
> Fix it by reading cs_char_data.hi under cs_char_data.lock and
> rejecting calls with -ENODEV once the interface is gone;
> cs_char_release() now steals the pointer under the lock like
> cs_hsi_client_remove() does, so the interface is stopped exactly
> once between them.
>
> Fixes: 7f62fe8a5851 ("HSI: cmt_speech: Add cmt-speech driver")
> Cc: stable@vger.kernel.org
>
> Assisted-by: GLM:5.3
> Signed-off-by: Shengzhuo Wei <me@cherr.cc>
No blank line above the assisted-by line.
> ---
> Verified on a KASAN kernel with a software HSI controller: opening the
> character device, unbinding the client and issuing the ioctl gives
why are you unbinding? You do know that will taint the kernel in the
future, and this is not a "normal" operation that a user could do,
right?
>
> KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017]
> RIP: 0010:cs_char_ioctl+0x29e/0x340
>
> and with the patch applied the same sequence returns -ENODEV.
> ---
> drivers/hsi/clients/cmt_speech.c | 47 ++++++++++++++++++++++++++++++++++------
> 1 file changed, 40 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/hsi/clients/cmt_speech.c b/drivers/hsi/clients/cmt_speech.c
> index 7226677ebde7..4325152a5a62 100644
> --- a/drivers/hsi/clients/cmt_speech.c
> +++ b/drivers/hsi/clients/cmt_speech.c
> @@ -732,6 +732,17 @@ static int cs_hsi_write_on_data(struct cs_hsi_iface *hi, unsigned int slot)
> return ret;
> }
>
> +static struct cs_hsi_iface *cs_char_hsi_get(struct cs_char *csdata)
> +{
> + struct cs_hsi_iface *hi;
> +
> + spin_lock_bh(&csdata->lock);
> + hi = csdata->hi;
> + spin_unlock_bh(&csdata->lock);
That is not a normal "get" type operation.
Why are you not using the proper reference counting structures that you
already have here?
thanks,
greg k-h
prev parent reply other threads:[~2026-08-28 10:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 8:09 Shengzhuo Wei
2026-08-28 10:45 ` Greg KH [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=2026082802-plod-scroll-3acb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=aaro.koskinen@iki.fi \
--cc=carlos.chinea@nokia.com \
--cc=joni.lapilainen@gmail.com \
--cc=kai.vehmanen@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=me@cherr.cc \
--cc=sre@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®