From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: linux-kernel@vger.kernel.org
Cc: Lee Jones <lee@kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>,
Jiri Kosina <jikos@kernel.org>,
linux-input@vger.kernel.org
Subject: Flood of Event data for report XX was too short (X vs X) messages in 7.0
Date: Tue, 14 Apr 2026 16:57:31 +0200 [thread overview]
Message-ID: <6256259.lOV4Wx5bFT@natalenko.name> (raw)
[-- Attachment #1: Type: text/plain, Size: 3012 bytes --]
Hello Lee.
After the 0a3fe972a7cb14 ("HID: core: Mitigate potential OOB by removing bogus memset()") commit I observe the following flood in dmesg:
kernel: hid_report_raw_event: 6 callbacks suppressed
kernel: hid-generic 0003:051D:0002.0005: Event data for report 22 was too short (4 vs 2)
kernel: hid-generic 0003:051D:0002.0005: Event data for report 22 was too short (4 vs 2)
kernel: hid-generic 0003:051D:0002.0005: Event data for report 22 was too short (4 vs 2)
This machine has got an APC UPS attached:
Bus 001 Device 007: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Once I unplug the UPS USB cable, the flood stops.
IIUC apart from the rest, the commit changes the message verbosity from debug to warning. Maybe hid_dbg_ratelimited() should be used instead?
Thank you.
---
lsusb -vv on this device:
Bus 001 Device 007: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Negotiated speed: Full Speed (12Mbps)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 [unknown]
bDeviceSubClass 0 [unknown]
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x051d American Power Conversion
idProduct 0x0002 Uninterruptible Power Supply
bcdDevice 1.06
iManufacturer 1 American Power Conversion
iProduct 2 Back-UPS BX1200MI FW:294201G -302201G
iSerial 3 9B2105A23830
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0022
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 [unknown]
bInterfaceProtocol 0
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.10
bCountryCode 33 US
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 745
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0006 1x 6 bytes
bInterval 10
Device Status: 0x0002
(Bus Powered)
Remote Wakeup Enabled
--
Oleksandr Natalenko, MSE
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2026-04-14 15:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6256259.lOV4Wx5bFT@natalenko.name \
--to=oleksandr@natalenko.name \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=lee@kernel.org \
--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