From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, Seungjin Bae <eeodqql09@gmail.com>
Subject: Re: [PATCH] Input: ims-pcu - fix heap-buffer-overflow in ims_pcu_process_data()
Date: Sun, 26 Jul 2026 08:04:49 -0400 [thread overview]
Message-ID: <20260725192000.stable-0010@kernel.org> (raw)
In-Reply-To: <CAAsoPpV1WtUsPRtuRHQb8VuCvMHYHG2K-NU-LKGhFL6rWBdZHA@mail.gmail.com>
> Could you please pick up the following mainline commit for all
> applicable stable trees?
>
> commit 875115b82c295277b81b6dfee7debc725f44e854
> Input: ims-pcu - fix heap-buffer-overflow in ims_pcu_process_data()
Queued for 6.18, 6.12, 6.6, 6.1, 5.15, and 5.10, along with the
follow-up logic-error fix that Fixes: it, thanks.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-07-26 12:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 15:55 [PATCH] Input: ims-pcu - fix heap-buffer-overflow in ims_pcu_process_data() Seungjin Bae
2026-07-26 12:04 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-19 22:34 pip-izony
2025-12-19 23:36 ` Dmitry Torokhov
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=20260725192000.stable-0010@kernel.org \
--to=sashal@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=eeodqql09@gmail.com \
--cc=linux-input@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