CVE-2026-80918 — HID: core: fix number/pointer type confusion on long items
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 3dc8fc083dbfeede7b63a0c07581192e97711365 and < bed7fe3a936b6bdd84671385951397ca673cf6e7≥ 3dc8fc083dbfeede7b63a0c07581192e97711365 and < aec2c2ec87d4ec1f098979f68cd81b29f031c8cb≥ 3dc8fc083dbfeede7b63a0c07581192e97711365 and < 634f498ea5d5e8e01f8d9414d4f45eeaf9ee1996≥ 3dc8fc083dbfeede7b63a0c07581192e97711365 and < abec577de5fc16cd5caae42f97cdcd0983c06d66≥ 3dc8fc083dbfeede7b63a0c07581192e97711365 and < dd8035dec26e98204d6e4a6e0cee5c4d329b3d7e≥ 3dc8fc083dbfeede7b63a0c07581192e97711365 and < 1fa1591efd417e39e5e164bebea8ca7a3837c469≥ 3dc8fc083dbfeede7b63a0c07581192e97711365 and < e60159f5ea60254a5c3de4ea4f2f939f0171031b≥ 3dc8fc083dbfeede7b63a0c07581192e97711365 and < e542edada3f79387c0ac2a528cebf01f4ef47df8 and 2 more≥ 3dc8fc083dbfeede7b63a0c07581192e97711365 and < 28abce951343fcec26e397610868efa4e1395c3fversion 3.12 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 27, 2026 · 12 reading(s) · max 0.18%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
11 on the record
- git.kernel.org/stable/c/e542edada3f79387c0ac2a528cebf01f4ef47df8
- git.kernel.org/stable/c/dd8035dec26e98204d6e4a6e0cee5c4d329b3d7e
- git.kernel.org/stable/c/abec577de5fc16cd5caae42f97cdcd0983c06d66
- git.kernel.org/stable/c/634f498ea5d5e8e01f8d9414d4f45eeaf9ee1996
- git.kernel.org/stable/c/bed7fe3a936b6bdd84671385951397ca673cf6e7
- nvd.nist.gov/vuln/detail/CVE-2026-80918
- github.com/advisories/GHSA-vppq-2m7c-f4xg
- git.kernel.org/stable/c/28abce951343fcec26e397610868efa4e1395c3f
- git.kernel.org/stable/c/e60159f5ea60254a5c3de4ea4f2f939f0171031b
- git.kernel.org/stable/c/1fa1591efd417e39e5e164bebea8ca7a3837c469
- git.kernel.org/stable/c/aec2c2ec87d4ec1f098979f68cd81b29f031c8cb
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 8h
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 8h
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 8h
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 8h
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 8h
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 8h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-80918 is "HID: core: fix number/pointer type confusion on long items", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.