Vulnerability · Published Sep 4, 2026 · Assigned by Linux

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

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 9% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 90.7% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official 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>

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.187-1DEBIAN-CVE-2026-80781
Debian:13linux6.12.107-1DEBIAN-CVE-2026-80781
Debian:14linux7.1.12-1DEBIAN-CVE-2026-80781
Debian:12linux-6.126.12.107-1~deb12u1DEBIAN-CVE-2026-80781
Ubuntu:22.04:LTSlinux5.15.0-202.212UBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-80781
Ubuntu:26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-aws5.15.0-1119.126UBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-80781
Ubuntu:26.04:LTSlinux-aws7.0.0-1016.17UBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-azure5.15.0-1125.134UBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-80781
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1124.133UBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-80781
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-gcp5.15.0-1120.130UBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-80781
Ubuntu:26.04:LTSlinux-gcp7.0.0-1016.18UBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-gke5.15.0-1115.121UBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-80781
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1102.110UBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-ibm5.15.0-1113.117UBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-80781
Ubuntu:26.04:LTSlinux-ibm7.0.0-1017.17UBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1114.120UBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-kvm5.15.0-1111.116UBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-197.207UBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1114.115UBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-80781
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-80781
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1070.72UBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1059.59UBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-80781
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1017.17UBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-oracle5.15.0-1116.122UBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-80781
Ubuntu:26.04:LTSlinux-oracle7.0.0-1015.16UBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-80781
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-80781
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-80781
Ubuntu:26.04:LTSlinux-riscv7.0.0-42.42.1UBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-80781
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-80781
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-80781

Affected products (as reported)

VendorProductVersions
Linux Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 465544b3d6602cfbdc2305d5cbfb7f4954353b631da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 4993e1ab85d7d3f4a40d81852170f9665483bbd81da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 313ead1abed945544703b100a12c5a10fdf784091da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before c1d9c16af51cc6ff92a5a062617d3b022dd010781da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before a38212687519f2a72f43e62dec1348a6904124041da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 9a1d7c5f0d82e8665715d5e47c9410c6a97e37481da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 5215ea00a747eca34cb2f603cfef91fef76c25581da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before cbcc0e8dea499e5ca86b583372ccb1815cccc570
Linux Linux 2.6.12

References