CVE-2026-80918

Not scored yetLast modified Oct 19, 2026

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.

Metrics

No CVSS score has been published yet.

Affected software

Source: the vendor's advisory (CNA). 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
Sep 9, 2026
Last modified
Oct 19, 2026
NVD status
Received

Related CVEs from 2026

CVE-2026-80919In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix recursive ww_mutex acquire in amdgpu_devcoredump_formatCVE-2026-80928.1Memory safety bugs present in Thunderbird ESR 140.10.1 and Thunderbird 150.0.1. Some of these bugs showed evidence of memory corruption and CVE-2026-80920In the Linux kernel, the following vulnerability has been resolved: io_uring: defer eventfd signaling when queued from a wakeup handler ioCVE-2026-809218.8In the Linux kernel, the following vulnerability has been resolved: KVM: s390: vsie: zero stale crypto bits When shadowing crypto access bCVE-2026-80922In the Linux kernel, the following vulnerability has been resolved: crypto: qcom-rng - Allow zero as a random number Zero is a valid randoCVE-2026-80923In the Linux kernel, the following vulnerability has been resolved: xhci: dbgtty: Fix unregister on tty_register_driver() failure If tty_rCVE-2026-809247.5In the Linux kernel, the following vulnerability has been resolved: crypto: krb5 - use kfree_sensitive() for derived key buffers crypto_krCVE-2026-80925In the Linux kernel, the following vulnerability has been resolved: vlan: fix skb_under_panic and races when toggling HW VLAN offload ToggCVE-2026-809269.8In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in oplock break notification smb2_oplock_breCVE-2026-80927In the Linux kernel, the following vulnerability has been resolved: timekeeping: Check the return value of tk_get_aux_ts64 in __do_adjtimexCVE-2026-809287.8In the Linux kernel, the following vulnerability has been resolved: smack: fix cred UAF in smack_file_send_sigiotask() When inspecting theCVE-2026-809297.8In the Linux kernel, the following vulnerability has been resolved: sysctl: move the "cad_pid" entry from pid_table[] to kern_reboot_table[
CVE-2026-80918: Unscored | Vulnix