From: Guo Zihao <guozh23@xiaopeng.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Markus Armbruster <armbru@redhat.com>,
Thomas Gleixner <tglx@kernel.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: [PATCH v2] Input: xen-kbdfront - bound the backend-supplied keycode
Date: Fri, 6 Nov 2026 10:02:17 +0800 [thread overview]
Message-ID: <20261106020217.48481-1-guozh23@xiaopeng.com> (raw)
In-Reply-To: <20261106014957.4130059-1-guozh23@xiaopeng.com>
Keycodes arrive from the shared ring the backend writes:
if (test_bit(key->keycode, info->ptr->keybit)) {
dev = info->ptr;
} else if (test_bit(key->keycode, info->kbd->keybit)) {
...
} else {
pr_warn("unhandled keycode 0x%x\n", key->keycode);
return;
}
The keycode is a plain u32 from the ring page, while the keybit
bitmaps it is tested against are sized for the KEY_CNT keycode bits
declared to the input core. A backend that sends a keycode at or
above KEY_CNT makes test_bit() read past the bitmap to decide which
device gets the event, and no keycode at or above KEY_MAX is a valid
EV_KEY code in the first place.
Since the event sits in memory the backend keeps writing access to,
the keycode must also be fetched exactly once: re-reading key->keycode
after the bounds check would let a concurrent backend write feed an
unchecked value to test_bit() and input_event(). Snapshot the keycode
into a local variable with READ_ONCE() before validating it, and use
the snapshot (as well as the already snapshotted pressed value)
throughout.
Ignore keycodes the bitmaps cannot hold.
Fixes: 4ee36dc08e5c ("xen pvfb: Para-virtual framebuffer, keyboard and pointer driver")
Cc: stable@vger.kernel.org
Signed-off-by: Guo Zihao <guozh23@xiaopeng.com>
---
v2: Snapshot the keycode with READ_ONCE() so a concurrent backend
write to the shared ring page cannot feed an unchecked value past the
KEY_MAX check (double-fetch, sashiko review); also reuse the already
snapshotted pressed value instead of re-reading key->pressed.
drivers/input/misc/xen-kbdfront.c | 16 +++++++++++-----
1 file changed, 11 insertions(+), 5 deletions(-)
diff --git a/drivers/input/misc/xen-kbdfront.c b/drivers/input/misc/xen-kbdfront.c
index 6471d836f6fe..f95aefedf026 100644
--- a/drivers/input/misc/xen-kbdfront.c
+++ b/drivers/input/misc/xen-kbdfront.c
@@ -91,22 +91,28 @@ static void xenkbd_handle_key_event(struct xenkbd_info *info,
{
struct input_dev *dev;
int value = key->pressed;
+ u32 keycode = READ_ONCE(key->keycode);
- if (test_bit(key->keycode, info->ptr->keybit)) {
+ if (keycode >= KEY_MAX) {
+ pr_warn("unhandled keycode 0x%x\n", keycode);
+ return;
+ }
+
+ if (test_bit(keycode, info->ptr->keybit)) {
dev = info->ptr;
- } else if (test_bit(key->keycode, info->kbd->keybit)) {
+ } else if (test_bit(keycode, info->kbd->keybit)) {
dev = info->kbd;
- if (key->pressed && test_bit(key->keycode, info->kbd->key))
+ if (value && test_bit(keycode, info->kbd->key))
value = 2; /* Mark as autorepeat */
} else {
- pr_warn("unhandled keycode 0x%x\n", key->keycode);
+ pr_warn("unhandled keycode 0x%x\n", keycode);
return;
}
if (unlikely(!dev))
return;
- input_event(dev, EV_KEY, key->keycode, value);
+ input_event(dev, EV_KEY, keycode, value);
input_sync(dev);
}
--
2.50.1
next prev parent reply other threads:[~2026-11-06 2:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 1:49 [PATCH] " Guo Zihao
2026-11-06 2:02 ` Guo Zihao [this message]
2026-11-06 6:21 ` [PATCH v2] " Dmitry Torokhov
2026-11-06 6:32 ` Guo Zihao
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=20261106020217.48481-1-guozh23@xiaopeng.com \
--to=guozh23@xiaopeng.com \
--cc=armbru@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@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®