From: Benjamin Tissoires <bentiss@kernel.org>
To: jikos@kernel.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, Qasim Ijaz <qasdev00@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH RESEND] HID: asus: fix UAF via HID_CLAIMED_INPUT validation
Date: Wed, 13 Aug 2025 11:43:29 +0200 [thread overview]
Message-ID: <175507820932.20076.1828761859413180643.b4-ty@kernel.org> (raw)
In-Reply-To: <20250810181041.44874-1-qasdev00@gmail.com>
On Sun, 10 Aug 2025 19:10:41 +0100, Qasim Ijaz wrote:
> After hid_hw_start() is called hidinput_connect() will eventually be
> called to set up the device with the input layer since the
> HID_CONNECT_DEFAULT connect mask is used. During hidinput_connect()
> all input and output reports are processed and corresponding hid_inputs
> are allocated and configured via hidinput_configure_usages(). This
> process involves slot tagging report fields and configuring usages
> by setting relevant bits in the capability bitmaps. However it is possible
> that the capability bitmaps are not set at all leading to the subsequent
> hidinput_has_been_populated() check to fail leading to the freeing of the
> hid_input and the underlying input device.
>
> [...]
Applied to hid/hid.git (for-6.17/upstream-fixes), thanks!
[1/1] HID: asus: fix UAF via HID_CLAIMED_INPUT validation
https://git.kernel.org/hid/hid/c/d3af6ca9a8c3
Cheers,
--
Benjamin Tissoires <bentiss@kernel.org>
prev parent reply other threads:[~2025-08-13 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-10 18:10 [PATCH RESEND] HID: asus: fix UAF via HID_CLAIMED_INPUT validation Qasim Ijaz
2025-08-13 9:43 ` Benjamin Tissoires [this message]
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=175507820932.20076.1828761859413180643.b4-ty@kernel.org \
--to=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qasdev00@gmail.com \
--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