CVE-2026-80781: Linux kernel · HID: core: fix OOB read of field->usage in hid_set_field()
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 26 Oct 2026, 17:16 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 4 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix has been implemented in the Linux kernel by reordering the code to perform the bounds check before dereferencing the pointer in hid_set_field(). Users should update to a kernel version that includes this fix once available.
Description
In the Linux kernel, the following vulnerability has been resolved: HID: core: fix OOB read of field->usage in hid_set_field() hid_set_field() hands field->usage + offset to hid_dump_input() before the guard that bounds offset: hid_dump_input(field->report->device, field->usage + offset, value); if (offset >= field->report_count) { hid_err(...); return -1; } Under CONFIG_DEBUG_FS hid_dump_input() dereferences that pointer, with buf = hid_resolv_usage(usage->hid, NULL). The usage[] array is allocated inline with the hid_field in hid_register_field() and holds field->maxusage entries, so an offset past it reads off the end of the kvzalloc()ed allocation and into a neighbouring object. Had the guard run first, offset < report_count <= maxusage would already have confined the pointer to the array. A caller supplies such an offset today. picolcd_fb_send_tile() validates only report->maxfield before issuing hid_set_field(report->field[0], 11 + i, ...) for i = 0..31, so its offsets are fixed at 11..42 and are never checked against the bound field. When the device registers that field with fewer usages, the framebuffer deferred-io work drives the read on every tile. KASAN reports a 4-byte slab-out-of-bounds read in hid_dump_input() below hid_set_field(), and the same boot logs "offset (1) exceeds report_count (1)" from the guard that runs only afterwards. Move the hid_dump_input() call below the guard. Because field->maxusage >= field->report_count, the guard then establishes that field->usage + offset lies inside the array before it is dereferenced, for every caller and without changing behaviour on the valid path. Discovered by XBOW, triaged by Baul Lee <baul.lee@xbow.com>
References
- nvd.nist.gov/vuln/detail/CVE-2026-80781 (opens in a new tab)
- git.kernel.org/stable/c/313ead1abed945544703b100a12c5a10fdf78409 (opens in a new tab)
- git.kernel.org/stable/c/465544b3d6602cfbdc2305d5cbfb7f4954353b63 (opens in a new tab)
- git.kernel.org/stable/c/4993e1ab85d7d3f4a40d81852170f9665483bbd8 (opens in a new tab)
- git.kernel.org/stable/c/5215ea00a747eca34cb2f603cfef91fef76c2558 (opens in a new tab)
- git.kernel.org/stable/c/9a1d7c5f0d82e8665715d5e47c9410c6a97e3748 (opens in a new tab)
- git.kernel.org/stable/c/a13cdb19fcb223ed41bdab3bab42b98dba87e90b (opens in a new tab)
- git.kernel.org/stable/c/a38212687519f2a72f43e62dec1348a690412404 (opens in a new tab)
- git.kernel.org/stable/c/c1d9c16af51cc6ff92a5a062617d3b022dd01078 (opens in a new tab)
- git.kernel.org/stable/c/cbcc0e8dea499e5ca86b583372ccb1815cccc570 (opens in a new tab)
- ubuntu.com/security/CVE-2026-80781 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-80781 (opens in a new tab)
- git.kernel.org/linus/a13cdb19fcb223ed41bdab3bab42b98dba87e90b (opens in a new tab)