public inbox for linux-input@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Jiri Kosina <jikos@kernel.org>
Cc: "Benjamin Tissoires" <bentiss@kernel.org>,
	"Filipe Laíns" <lains@riseup.net>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HID: logitech-dj: fix wrong detection of bad DJ_SHORT output report
Date: Mon, 13 Apr 2026 14:15:35 +0100	[thread overview]
Message-ID: <20260413131535.GA10076@google.com> (raw)
In-Reply-To: <2qo95np2-n977-9r09-p016-880q98025q44@xreary.bet>

On Fri, 10 Apr 2026, Jiri Kosina wrote:

> On Fri, 10 Apr 2026, Benjamin Tissoires wrote:
> 
> > commit b6a57912854e ("HID: logitech-dj: Prevent REPORT_ID_DJ_SHORT
> > related user initiated OOB write") assumed that all HID devices attached
> > to the logitech-dj driver was having an output report of DJ_SHORT.
> > 
> > However, on the receiver itself, we have 2 other HID device we attach
> > here: the mouse emulation and the keyboard emulation. For those devices
> > the value of rep is NULL and we are triggered a segfault here.
> > 
> > This is doubly required because logitech-dj also handles non DJ devices
> > that might not have the DJ collection.
> > 
> > Fixes: b6a57912854e ("HID: logitech-dj: Prevent REPORT_ID_DJ_SHORT related user initiated OOB write")
> > Signed-off-by: Benjamin Tissoires <bentiss@kernel.org>
> 
> Thanks a lot Benjamin, your CI be praised!

Thanks Benjamin.  I appreciate your work.

If it's not too late:

  Reviewed-by: Lee Jones <lee@kernel.org>

-- 
Lee Jones [李琼斯]

      reply	other threads:[~2026-04-13 13:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10 14:03 [PATCH] HID: logitech-dj: fix wrong detection of bad DJ_SHORT output report Benjamin Tissoires
2026-04-10 15:23 ` Jiri Kosina
2026-04-13 13:15   ` Lee Jones [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=20260413131535.GA10076@google.com \
    --to=lee@kernel.org \
    --cc=bentiss@kernel.org \
    --cc=jikos@kernel.org \
    --cc=lains@riseup.net \
    --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