All of lore.kernel.org
 help / color / mirror / Atom feed
From: Davide Beatrici <me@davidebeatrici.dev>
To: Terry Junge <linuxhid@cosmicgizmosystems.com>
Cc: Benjamin Tissoires <bentiss@kernel.org>,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
	jikos@kernel.org, benjamin.tissoires@redhat.com
Subject: Re: [PATCH] HID: validate report length and constants
Date: Tue, 02 Dec 2025 22:54:26 +0100	[thread overview]
Message-ID: <9e44de7bab6967a200d7404ebb068071@davidebeatrici.dev> (raw)
In-Reply-To: <91117308-7eb5-4258-ac87-1afb2d46d2b5@cosmicgizmosystems.com>

> Can you supply the Device, Configuration, and Report Descriptors?

Sure.

Device Descriptor:
   idVendor           0x373b Compx
   idProduct          0x1107 ATK X1 SE Nearlink
   bcdDevice          1.21
   bcdUSB             2.00
   bMaxPacketSize0    64
   iManufacturer      1 Compx
   iProduct           2 ATK X1 SE Nearlink
   bNumConfigurations 1

Configuration Descriptor:
   wTotalLength       0x0054
   bNumInterfaces     3
   bmAttributes       0xa0 (Bus Powered, Remote Wakeup)
   MaxPower           494mA

Interface 0: HID Keyboard
   HID Descriptor: wDescriptorLength 77
   Endpoint IN 0x81, Interrupt, 64 bytes

Interface 1: HID (non‑boot)
   HID Descriptor: wDescriptorLength 156
   Endpoint IN 0x82, Interrupt, 64 bytes

Interface 2: HID Mouse
   HID Descriptor: wDescriptorLength 87
   Endpoint IN 0x83, Interrupt, 64 bytes

Report Descriptors:

Interface 2 (Mouse):
   05 01 09 02 A1 01 09 01 A1 00 05 09 19 01 29 05
   15 00 25 01 95 05 75 01 81 02 95 01 75 03 81 01
   05 01 09 30 09 31 16 00 80 26 FF 7F 75 10 95 02
   81 06 C0 A1 00 05 01 09 38 15 81 25 7F 75 08 95
   01 81 06 C0 A1 00 05 0C 0A 38 02 95 01 75 08 15
   81 25 7F 81 06 C0 C0

Interface 1 (HID composite):
   05 0C 09 01 A1 01 85 05 15 00 26 14 05 19 00 2A
   14 05 75 10 95 01 81 00 C0 05 01 09 80 A1 01 85
   03 19 81 29 83 15 00 25 01 95 03 75 01 81 02 95
   01 75 05 81 01 C0 05 01 09 06 A1 01 85 04 05 07
   15 00 25 01 19 00 29 9F 95 A0 75 01 81 02 C0 06
   02 FF 09 02 A1 01 85 13 15 00 26 FF 00 75 08 95
   13 09 02 81 00 09 02 91 00 C0 06 02 FF 09 02 A1
   01 85 08 15 00 26 FF 00 75 08 95 10 09 02 81 00
   09 02 91 00 C0 06 04 FF 09 02 A1 01 85 06 09 02
   15 00 26 FF 00 75 08 95 07 B1 02 C0

Interface 0 (Keyboard):
   05 01 09 06 A1 01 05 08 19 01 29 03 15 00 25 01
   75 01 95 03 91 02 95 05 91 01 05 07 19 E0 29 E7
   15 00 25 01 75 01 95 08 81 02 75 08 95 01 81 01
   05 07 19 00 2A FF 00 15 00 26 FF 00 75 08 95 05
   81 00 05 FF 09 03 75 08 95 01 81 02 C0

  reply	other threads:[~2025-12-02 21:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-02  5:36 [PATCH] HID: validate report length and constants Davide Beatrici
2025-12-02  8:22 ` Benjamin Tissoires
2025-12-02 19:41   ` Davide Beatrici
2025-12-02 21:40     ` Terry Junge
2025-12-02 21:54       ` Davide Beatrici [this message]
2025-12-04  9:53         ` Benjamin Tissoires
2025-12-04 19:48           ` Davide Beatrici
2025-12-04 23:43             ` Davide Beatrici
2025-12-08  8:54               ` Benjamin Tissoires
2025-12-12  6:22                 ` Davide Beatrici

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=9e44de7bab6967a200d7404ebb068071@davidebeatrici.dev \
    --to=me@davidebeatrici.dev \
    --cc=benjamin.tissoires@redhat.com \
    --cc=bentiss@kernel.org \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxhid@cosmicgizmosystems.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.