HID: core: fix number/pointer type confusion on long items
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.267, 5.15.218, 6.1.185, 6.6.154, 6.12.106, and 3 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 3dc8fc083dbfeede7b63a0c07581192e97711365 · fixed in bed7fe3a936b6bdd84671385951397ca673cf6e7; From 3dc8fc083dbfeede7b63a0c07581192e97711365 · fixed in aec2c2ec87d4ec1f098979f68cd81b29f031c8cb; From 3dc8fc083dbfeede7b63a0c07581192e97711365 · fixed in 634f498ea5d5e8e01f8d9414d4f45eeaf9ee1996; From 3dc8fc083dbfeede7b63a0c07581192e97711365 · fixed in abec577de5fc16cd5caae42f97cdcd0983c06d66; From 3dc8fc083dbfeede7b63a0c07581192e97711365 · fixed in dd8035dec26e98204d6e4a6e0cee5c4d329b3d7e; From 3dc8fc083dbfeede7b63a0c07581192e97711365 · fixed in 1fa1591efd417e39e5e164bebea8ca7a3837c469; From 3dc8fc083dbfeede7b63a0c07581192e97711365 · fixed in e60159f5ea60254a5c3de4ea4f2f939f0171031b; From 3dc8fc083dbfeede7b63a0c07581192e97711365 · fixed in e542edada3f79387c0ac2a528cebf01f4ef47df8; From 3dc8fc083dbfeede7b63a0c07581192e97711365 · fixed in 28abce951343fcec26e397610868efa4e1395c3f
- Linux Linux
3.12
- KernelLinux
From 3.12.0 · fixed in 5.10.267; From 5.11.0 · fixed in 5.15.218; From 5.16.0 · fixed in 6.1.185; From 6.2.0 · fixed in 6.6.154; From 6.7.0 · fixed in 6.12.106; From 6.13.0 · fixed in 6.18.47; From 6.19.0 · fixed in 7.1.11; From 7.2.0 · fixed in 7.2.1
References 9
git.kernel.org
- stable/c/bed7fe3a936b6bdd84671385951397ca673cf6e7
- stable/c/aec2c2ec87d4ec1f098979f68cd81b29f031c8cb
- stable/c/634f498ea5d5e8e01f8d9414d4f45eeaf9ee1996
- stable/c/abec577de5fc16cd5caae42f97cdcd0983c06d66
- stable/c/dd8035dec26e98204d6e4a6e0cee5c4d329b3d7e
- stable/c/1fa1591efd417e39e5e164bebea8ca7a3837c469
- stable/c/e60159f5ea60254a5c3de4ea4f2f939f0171031b
- stable/c/e542edada3f79387c0ac2a528cebf01f4ef47df8
- stable/c/28abce951343fcec26e397610868efa4e1395c3f