From: Duoming Zhou <duoming@zju.edu.cn>
To: linux-input@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, dmitry.torokhov@gmail.com,
pali@kernel.org, kuba@kernel.org, alexander.deucher@amd.com,
akpm@linux-foundation.org, johannes.berg@intel.com,
pkshih@realtek.com, hverkuil+cisco@kernel.org,
andriy.shevchenko@linux.intel.com, tglx@linutronix.de,
mingo@kernel.org, Duoming Zhou <duoming@zju.edu.cn>
Subject: [PATCH v2 RESEND 0/2] Input: alps/psmouse: Fix UAF bugs and improve workqueue synchronization
Date: Wed, 17 Dec 2025 11:00:16 +0800 [thread overview]
Message-ID: <cover.1765939397.git.duoming@zju.edu.cn> (raw)
This patch series addresses use-after-free bugs in the ALPS
touchpad driver and enhances workqueue handling efficiency
in the psmouse subsystem.
The first patch fixes a critical use-after-free race condition
in the ALPS driver where dev3_register_work could be scheduled
after the alps_data structure was already freed. This was caused
by insufficient synchronization during device disconnection,
where flush_workqueue() couldn't prevent subsequent work item
submissions.
The second patch optimizes the psmouse disconnect path by replacing
flush_workqueue() with disable_delayed_work_sync() for better
efficiency and robustness.
Duoming Zhou (2):
Input: alps - fix use-after-free bugs caused by dev3_register_work
Input: psmouse - Replace flush_workqueue() with
disable_delayed_work_sync()
drivers/input/mouse/alps.c | 1 +
drivers/input/mouse/psmouse-base.c | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
--
2.34.1
next reply other threads:[~2025-12-17 3:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 3:00 Duoming Zhou [this message]
2025-12-17 3:00 ` [PATCH v2 RESEND 1/2] Input: alps - fix use-after-free bugs caused by dev3_register_work Duoming Zhou
2025-12-17 18:08 ` Dmitry Torokhov
2025-12-17 3:00 ` [PATCH v2 RESEND 2/2] Input: psmouse - Replace flush_workqueue() with disable_delayed_work_sync() Duoming Zhou
2025-12-17 18:13 ` Dmitry Torokhov
2025-12-18 5:49 ` duoming
2025-12-18 6:58 ` Dmitry Torokhov
2025-12-18 14:25 ` duoming
2025-12-27 15:58 ` Andy Shevchenko
2025-12-28 23:15 ` 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=cover.1765939397.git.duoming@zju.edu.cn \
--to=duoming@zju.edu.cn \
--cc=akpm@linux-foundation.org \
--cc=alexander.deucher@amd.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hverkuil+cisco@kernel.org \
--cc=johannes.berg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pali@kernel.org \
--cc=pkshih@realtek.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).