From: Pavel Machek <pavel@denx.de>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
"Tomasz Pakuła" <forest10pl@gmail.com>,
"Nolan Nicholson" <nolananicholson@gmail.com>,
"Tomasz Pakuła" <tomasz.pakula.oficjalny@gmail.com>,
"Michał Kopeć" <michal@nozomi.space>,
"Paul Dino Jones" <paul@spacefreak18.xyz>,
"Cristóferson Bueno" <cbueno81@gmail.com>,
"Pablo Cisneros" <patchkez@protonmail.com>,
"Jiri Kosina" <jkosina@suse.com>,
jikos@kernel.org, bentiss@kernel.org, linux-usb@vger.kernel.org,
linux-input@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 5.10 3/5] HID: pidff: Fix null pointer dereference in pidff_find_fields
Date: Fri, 18 Apr 2025 18:57:11 +0200 [thread overview]
Message-ID: <aAKEZwyixI01sJmk@duo.ucw.cz> (raw)
In-Reply-To: <20250331145716.1706253-3-sashal@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]
Hi!
> From: Tomasz Pakuła <forest10pl@gmail.com>
>
> [ Upstream commit 22a05462c3d0eee15154faf8d13c49e6295270a5 ]
>
> This function triggered a null pointer dereference if used to search for
> a report that isn't implemented on the device. This happened both for
> optional and required reports alike.
Ok.
> +++ b/drivers/hid/usbhid/hid-pidff.c
> @@ -770,6 +770,11 @@ static void pidff_set_autocenter(struct input_dev *dev, u16 magnitude)
> static int pidff_find_fields(struct pidff_usage *usage, const u8 *table,
> struct hid_report *report, int count, int strict)
> {
> + if (!report) {
> + pr_debug("pidff_find_fields, null report\n");
> + return -1;
> + }
> +
> int i, j, k, found;
>
> for (k = 0; k < count; k++) {
> @@ -883,6 +888,11 @@ static int pidff_reports_ok(struct pidff_device *pidff)
> static struct hid_field *pidff_find_special_field(struct hid_report *report,
> int usage, int enforce_min)
> {
> + if (!report) {
> + pr_debug("pidff_find_special_field, null report\n");
> + return NULL;
> + }
> +
> int i;
But this is quite strange. Normally declarations go first. Not sure if
old compilers can handle this?
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2025-04-18 16:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 14:57 [PATCH AUTOSEL 5.10 1/5] HID: pidff: Convert infinite length from Linux API to PID standard Sasha Levin
2025-03-31 14:57 ` [PATCH AUTOSEL 5.10 2/5] HID: pidff: Do not send effect envelope if it's empty Sasha Levin
2025-03-31 14:57 ` [PATCH AUTOSEL 5.10 3/5] HID: pidff: Fix null pointer dereference in pidff_find_fields Sasha Levin
2025-04-18 16:57 ` Pavel Machek [this message]
2025-03-31 14:57 ` [PATCH AUTOSEL 5.10 4/5] ALSA: hda: intel: Fix Optimus when GPU has no sound Sasha Levin
2025-03-31 14:57 ` [PATCH AUTOSEL 5.10 5/5] ALSA: usb-audio: Fix CME quirk for UF series keyboards Sasha Levin
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=aAKEZwyixI01sJmk@duo.ucw.cz \
--to=pavel@denx.de \
--cc=bentiss@kernel.org \
--cc=cbueno81@gmail.com \
--cc=forest10pl@gmail.com \
--cc=jikos@kernel.org \
--cc=jkosina@suse.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michal@nozomi.space \
--cc=nolananicholson@gmail.com \
--cc=patchkez@protonmail.com \
--cc=paul@spacefreak18.xyz \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tomasz.pakula.oficjalny@gmail.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
all inboxes | Powered by JetHome®