VDB

CVE-2026-80781

CVE-2026-80781 PUBLISHED

HID: core: fix OOB read of field->usage in hid_set_field()

Reported by linux · Published September 4, 2026

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>

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
kernel6.18Amazon Linux1:6.18.48-107.148.amzn2023
kernel6.18-develAmazon Linux1:6.18.48-107.148.amzn2023
kernel6.12-modules-extraAmazon Linux1:6.12.110-135.201.amzn2023
bpftool6.18Amazon Linux1:6.18.48-107.148.amzn2023
kernel6.18-headersAmazon Linux1:6.18.48-107.148.amzn2023

Affected products

VendorProductVersions
LinuxLinux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2
LinuxLinux2.6.12, 0, 5.10.267
amazon:2023kernel6.180
amazon:2023kernel6.18-devel0
amazon:2023kernel6.12-modules-extra0
amazon:2023bpftool6.180
amazon:2023kernel6.18-headers0
linuxlinux_kernel2.6.12, 2.6.12, 2.6.12
amazon:2023kernel6.120
amazon:2023bpftool0
amazon:2023kernel6.18-tools0
amazon:2023kernel-livepatch-6.1.186-228.3740
amazon:2023kernel-devel0
amazon:2023kernel6.12-headers0
amazon:2023kernel-tools0
amazon:2023kernel6.18-modules-extra-common0
amazon:2023kernel-headers0
amazon:2023perf6.120
amazon:2023kernel-livepatch-6.18.48-107.1480
amazon:2023kernel-livepatch-6.12.110-135.2010

…and 18 more

Timeline

  • Sep 4, 2026 Coalition ESS Score
  • Sep 4, 2026 CVE Published
  • Sep 5, 2026 EPSS Score (13 in total, the first dated here)
  • Nov 6, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-80781
vulnetix vdb fixes CVE-2026-80781

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-80781/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›