From: "Habil Eren Türker" <habilerenturker@gmail.com>
To: dmitry.torokhov@gmail.com
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
"Habil Eren Türker" <habilerenturker@hotmail.com>
Subject: [PATCH] Input: fix potential use-after-free in input_devices_seq_show
Date: Mon, 28 Sep 2026 19:56:48 +0300 [thread overview]
Message-ID: <20260928170051.58695-1-habilerenturker@hotmail.com> (raw)
The input_devices_seq_show() function accesses the input_dev structure
while holding input_mutex. However, the device can still be freed
concurrently, leading to a use-after-free.
Fix this by taking a reference to the input device in
input_devices_seq_start() and dropping it in input_devices_seq_stop().
Tested-by: Habil Eren Türker <habilerenturker@hotmail.com>
Signed-off-by: Habil Eren Türker <habilerenturker@hotmail.com>
---
drivers/input/input.c | 20 ++++++++++++++++++--
1 file changed, 18 insertions(+), 2 deletions(-)
diff --git a/drivers/input/input.c b/drivers/input/input.c
index cf6fecea7..14a95e816 100644
--- a/drivers/input/input.c
+++ b/drivers/input/input.c
@@ -1051,6 +1051,7 @@ static __poll_t input_proc_devices_poll(struct file *file, poll_table *wait)
static void *input_devices_seq_start(struct seq_file *seq, loff_t *pos)
{
struct input_seq_state *state = seq->private;
+ void *v;
int error;
error = mutex_lock_interruptible(&input_mutex);
@@ -1061,7 +1062,11 @@ static void *input_devices_seq_start(struct seq_file *seq, loff_t *pos)
state->mutex_acquired = true;
- return seq_list_start(&input_dev_list, *pos);
+ v = seq_list_start(&input_dev_list, *pos);
+ if (v)
+ input_get_device(container_of(v, struct input_dev, node));
+
+ return v;
}
static void *input_devices_seq_next(struct seq_file *seq, void *v, loff_t *pos)
@@ -1077,6 +1082,17 @@ static void input_seq_stop(struct seq_file *seq, void *v)
mutex_unlock(&input_mutex);
}
+static void input_devices_seq_stop(struct seq_file *seq, void *v)
+{
+ struct input_seq_state *state = seq->private;
+
+ if (v)
+ input_put_device(container_of(v, struct input_dev, node));
+
+ if (state->mutex_acquired)
+ mutex_unlock(&input_mutex);
+}
+
static void input_seq_print_bitmap(struct seq_file *seq, const char *name,
unsigned long *bitmap, int max)
{
@@ -1151,7 +1167,7 @@ static int input_devices_seq_show(struct seq_file *seq, void *v)
static const struct seq_operations input_devices_seq_ops = {
.start = input_devices_seq_start,
.next = input_devices_seq_next,
- .stop = input_seq_stop,
+ .stop = input_devices_seq_stop,
.show = input_devices_seq_show,
};
--
2.47.3
next reply other threads:[~2026-09-28 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 16:56 Habil Eren Türker [this message]
2026-09-28 17:09 ` [PATCH] Input: fix potential use-after-free in input_devices_seq_show sashiko-bot
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=20260928170051.58695-1-habilerenturker@hotmail.com \
--to=habilerenturker@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=habilerenturker@hotmail.com \
--cc=linux-input@vger.kernel.org \
--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