CVE-2026-80918

Unknown

Last modified

CVE-2026-80918 is a vulnerability of currently unknown severity. 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..

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 Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 3dc8fc083dbfeede7b63a0c07581192e97711365, < bed7fe3a936b6bdd84671385951397ca673cf6e7; >= 3dc8fc083dbfeede7b63a0c07581192e97711365, < aec2c2ec87d4ec1f098979f68cd81b29f031c8cb; >= 3dc8fc083dbfeede7b63a0c07581192e97711365, < 634f498ea5d5e8e01f8d9414d4f45eeaf9ee1996; >= 3dc8fc083dbfeede7b63a0c07581192e97711365, < abec577de5fc16cd5caae42f97cdcd0983c06d66; >= 3dc8fc083dbfeede7b63a0c07581192e97711365, < dd8035dec26e98204d6e4a6e0cee5c4d329b3d7e; >= 3dc8fc083dbfeede7b63a0c07581192e97711365, < 1fa1591efd417e39e5e164bebea8ca7a3837c469; >= 3dc8fc083dbfeede7b63a0c07581192e97711365, < e60159f5ea60254a5c3de4ea4f2f939f0171031b; >= 3dc8fc083dbfeede7b63a0c07581192e97711365, < e542edada3f79387c0ac2a528cebf01f4ef47df8; >= 3dc8fc083dbfeede7b63a0c07581192e97711365, < 28abce951343fcec26e397610868efa4e1395c3f
LinuxLinux3.12

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-80918?
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.
How severe is CVE-2026-80918?
Severity scoring for CVE-2026-80918 is pending analysis.
How do I fix CVE-2026-80918?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-80918?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST