CVE-2026-80918

HID: core: fix number/pointer type confusion on long items

N/A
Published: September 9, 2026 at 04:13 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: HID: core: fix number/pointer type confusion on long items When fetch_item() is called by hid_scan_report() on an item with HID_ITEM_TAG_LONG, it stores a pointer to the item data in item->data.longdata instead of storing a value directly in item->data.{u8/u16/u32}. When item_udata() or item_sdata() encounters such an item, it incorrectly assumes that the item is in short format, and therefore returns the lower part of a kernel pointer reinterpreted as a number. When a HID device is connected whose descriptor contains a HID_GLOBAL_ITEM_TAG_REPORT_SIZE encoded in long format with size=4, this causes the lower half of a kernel pointer to be printed into dmesg as a number, like this: hid (null): invalid report_size 107953555 To fix it, let item_udata() and item_sdata() verify that the item is in short format. Note that this bug only affects hid_scan_report(), while the main parsing pass hid_parse_collections() will always bail out when encountering a long item. Sidenote: There are currently no users of data.longdata; maybe we should just remove any parsing of long-format descriptors as a follow-up.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.123dc8fc083dbfeede7b63a0c07581192e97711365
Vendor states this is fixed in 1fa1591efd417e39e5e164bebea8ca7a3837c469 (fixed)
Vendor states this is fixed in 28abce951343fcec26e397610868efa4e1395c3f (fixed)
Vendor states this is fixed in 634f498ea5d5e8e01f8d9414d4f45eeaf9ee1996 (fixed)
Vendor states this is fixed in abec577de5fc16cd5caae42f97cdcd0983c06d66 (fixed)
Vendor states this is fixed in aec2c2ec87d4ec1f098979f68cd81b29f031c8cb (fixed)
Vendor states this is fixed in bed7fe3a936b6bdd84671385951397ca673cf6e7 (fixed)
Vendor states this is fixed in dd8035dec26e98204d6e4a6e0cee5c4d329b3d7e (fixed)
Vendor states this is fixed in e542edada3f79387c0ac2a528cebf01f4ef47df8 (fixed)
Vendor states this is fixed in e60159f5ea60254a5c3de4ea4f2f939f0171031b (fixed)
Vendor states this is fixed in 3.12 (unaffected)
Vendor states this is fixed in 5.10.267 (unaffected)
Vendor states this is fixed in 5.15.218 (unaffected)
Vendor states this is fixed in 6.1.185 (unaffected)
Vendor states this is fixed in 6.12.106 (unaffected)
Vendor states this is fixed in 6.18.47 (unaffected)
Vendor states this is fixed in 6.6.154 (unaffected)
Vendor states this is fixed in 7.1.11 (unaffected)
Vendor states this is fixed in 7.2.1 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card