From: Hyeonsu Choi <chlgustn3171@gmail.com>
To: Jiri Kosina <jikos@kernel.org>, Benjamin Tissoires <bentiss@kernel.org>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Hyeonsu Choi <chlgustn3171@gmail.com>,
syzbot+aec1962419768c5caf88@syzkaller.appspotmail.com
Subject: [PATCH] HID: input: allocate input_dev name/phys/uniq using hid device devres
Date: Tue, 14 Jul 2026 21:00:52 +0900 [thread overview]
Message-ID: <20260714120052.255085-1-chlgustn3171@gmail.com> (raw)
input_dev->name, phys, and uniq are directly assigned from hid_device.
It causes a slab-use-after-free bug if the input device outlives the parent HID device during teardown.
Fix this by using devm_kstrdup() tied to &hid->dev for name, phys, and uniq strings.
The string lifetime is tied to the parent HID device, preventing a potential slab-use-after-free bug.
Also add OOM error handling for these allocations.
Reported-by: syzbot+aec1962419768c5caf88@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=aec1962419768c5caf88
Signed-off-by: Hyeonsu Choi <chlgustn3171@gmail.com>
---
drivers/hid/hid-input.c | 19 ++++++++++++++++---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/drivers/hid/hid-input.c b/drivers/hid/hid-input.c
index 3487600cadb4..da6b338f18ba 100644
--- a/drivers/hid/hid-input.c
+++ b/drivers/hid/hid-input.c
@@ -2125,10 +2125,21 @@ static struct hid_input *hidinput_allocate(struct hid_device *hid,
input_dev->close = hidinput_close;
input_dev->setkeycode = hidinput_setkeycode;
input_dev->getkeycode = hidinput_getkeycode;
+
+ const char *name = hidinput->name ? hidinput->name : hid->name;
+
+ input_dev->name = devm_kstrdup(&hid->dev, name, GFP_KERNEL);
+ if (!input_dev->name)
+ goto fail;
+
+ input_dev->phys = devm_kstrdup(&hid->dev, hid->phys, GFP_KERNEL);
+ if (!input_dev->phys)
+ goto fail;
+
+ input_dev->uniq = devm_kstrdup(&hid->dev, hid->uniq, GFP_KERNEL);
+ if (!input_dev->uniq)
+ goto fail;
- input_dev->name = hidinput->name ? hidinput->name : hid->name;
- input_dev->phys = hid->phys;
- input_dev->uniq = hid->uniq;
input_dev->id.bustype = hid->bus;
input_dev->id.vendor = hid->vendor;
input_dev->id.product = hid->product;
@@ -2144,6 +2155,8 @@ static struct hid_input *hidinput_allocate(struct hid_device *hid,
return hidinput;
fail:
+ if (hidinput)
+ kfree(hidinput->name);
kfree(hidinput);
input_free_device(input_dev);
hid_err(hid, "Out of memory during hid input probe\n");
--
2.53.0
next reply other threads:[~2026-07-14 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 12:00 Hyeonsu Choi [this message]
2026-07-14 12:18 ` [PATCH] HID: input: allocate input_dev name/phys/uniq using hid device devres sashiko-bot
2026-07-14 13:33 ` chlgustn3171
2026-07-14 13:39 ` chlgustn3171
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=20260714120052.255085-1-chlgustn3171@gmail.com \
--to=chlgustn3171@gmail.com \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+aec1962419768c5caf88@syzkaller.appspotmail.com \
/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