CVE-2026-80918
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
Propose a mitigation on Community Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
Debian Fixed 4 releases
| Version | Status | Fixed in |
|---|---|---|
| trixie | Fixed | 6.12.107-1 |
| sid | Fixed | 7.1.12-1 |
| forky | Fixed | 7.1.12-1 |
| bookworm | Fixed | 6.1.187-1 |
References
- https://git.kernel.org/stable/c/1fa1591efd417e39e5e164bebea8ca7a3837c469
- https://git.kernel.org/stable/c/28abce951343fcec26e397610868efa4e1395c3f
- https://git.kernel.org/stable/c/634f498ea5d5e8e01f8d9414d4f45eeaf9ee1996
- https://git.kernel.org/stable/c/abec577de5fc16cd5caae42f97cdcd0983c06d66
- https://git.kernel.org/stable/c/aec2c2ec87d4ec1f098979f68cd81b29f031c8cb
- https://git.kernel.org/stable/c/bed7fe3a936b6bdd84671385951397ca673cf6e7
- https://git.kernel.org/stable/c/dd8035dec26e98204d6e4a6e0cee5c4d329b3d7e
- https://git.kernel.org/stable/c/e542edada3f79387c0ac2a528cebf01f4ef47df8
- https://git.kernel.org/stable/c/e60159f5ea60254a5c3de4ea4f2f939f0171031b
- https://security-tracker.debian.org/tracker/CVE-2026-80918
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.