CVE-2026-80918
CVE CVE-2026-80918EUVD EUVD-2026-75093Published 2026-09-09T16:13:15.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 3dc8fc083dbfeede7b63a0c07581192e97711365 <bed7fe3a936b6bdd84671385951397ca673cf6e7; 3dc8fc083dbfeede7b63a0c07581192e97711365 <634f498ea5d5e8e01f8d9414d4f45eeaf9ee1996; 3dc8fc083dbfeede7b63a0c07581192e97711365 <dd8035dec26e98204d6e4a6e0cee5c4d329b3d7e; 3.12; patch: 0; 3dc8fc083dbfeede7b63a0c07581192e97711365 <1fa1591efd417e39e5e164bebea8ca7a3837c469; patch: 6.12.106; patch: 5.10.267; patch: 6.18.47; patch: 7.3-rc1; patch: 5.15.218; 3dc8fc083dbfeede7b63a0c07581192e97711365 <28abce951343fcec26e397610868efa4e1395c3f; patch: 6.6.154; 3dc8fc083dbfeede7b63a0c07581192e97711365 <e542edada3f79387c0ac2a528cebf01f4ef47df8; 3dc8fc083dbfeede7b63a0c07581192e97711365 <e60159f5ea60254a5c3de4ea4f2f939f0171031b; patch: 7.2.1; 3dc8fc083dbfeede7b63a0c07581192e97711365 <aec2c2ec87d4ec1f098979f68cd81b29f031c8cb; 3dc8fc083dbfeede7b63a0c07581192e97711365 <abec577de5fc16cd5caae42f97cdcd0983c06d66; patch: 7.1.11; patch: 6.1.185
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.