CVE-2026-80781HID: core: fix OOB read of field->usage in hid_set_field()
- —Not scoredno CVSS score yet
- 0.19%Exploitation in 30 daysEPSS · top 91% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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 <[email protected]>
Timeline
ID reserved
By Linux
- 9 days later
· 9 days later
Published
- 2 months later
· 2 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.19% · top 91% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 465544b3d6602cfbdc2305d5cbfb7f4954353b63
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 4993e1ab85d7d3f4a40d81852170f9665483bbd8
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 313ead1abed945544703b100a12c5a10fdf78409
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < c1d9c16af51cc6ff92a5a062617d3b022dd01078
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a38212687519f2a72f43e62dec1348a690412404
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 9a1d7c5f0d82e8665715d5e47c9410c6a97e3748
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 5215ea00a747eca34cb2f603cfef91fef76c2558
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < cbcc0e8dea499e5ca86b583372ccb1815cccc570
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a13cdb19fcb223ed41bdab3bab42b98dba87e90b
- affected 2.6.12
- unaffected < 2.6.12
- unaffected 5.10.267 – ≤ 5.10.*
- unaffected 5.15.218 – ≤ 5.15.*
- unaffected 6.1.185 – ≤ 6.1.*
- unaffected 6.6.154 – ≤ 6.6.*
- unaffected 6.12.106 – ≤ 6.12.*
- unaffected 6.18.47 – ≤ 6.18.*
- unaffected 7.1.11 – ≤ 7.1.*
- unaffected 7.2.1 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References9
- https://git.kernel.org/stable/c/465544b3d6602cfbdc2305d5cbfb7f4954353b63 (opens in a new tab)
- https://git.kernel.org/stable/c/4993e1ab85d7d3f4a40d81852170f9665483bbd8 (opens in a new tab)
- https://git.kernel.org/stable/c/313ead1abed945544703b100a12c5a10fdf78409 (opens in a new tab)
- https://git.kernel.org/stable/c/c1d9c16af51cc6ff92a5a062617d3b022dd01078 (opens in a new tab)
- https://git.kernel.org/stable/c/a38212687519f2a72f43e62dec1348a690412404 (opens in a new tab)
- https://git.kernel.org/stable/c/9a1d7c5f0d82e8665715d5e47c9410c6a97e3748 (opens in a new tab)
- https://git.kernel.org/stable/c/5215ea00a747eca34cb2f603cfef91fef76c2558 (opens in a new tab)
- https://git.kernel.org/stable/c/cbcc0e8dea499e5ca86b583372ccb1815cccc570 (opens in a new tab)
- https://git.kernel.org/stable/c/a13cdb19fcb223ed41bdab3bab42b98dba87e90b (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-71424 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-80781)Record last updated .