Unknown

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

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>

Published Sep 4, 2026 · Updated Oct 19, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

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.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.2%

ahead of 9% of scored CVEs · Oct 26, 2026

Affects

Linux

CVSS base

—

Score not published yet.

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	≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 465544b3d6602cfbdc2305d5cbfb7f4954353b63≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 4993e1ab85d7d3f4a40d81852170f9665483bbd8≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 313ead1abed945544703b100a12c5a10fdf78409≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < c1d9c16af51cc6ff92a5a062617d3b022dd01078≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < a38212687519f2a72f43e62dec1348a690412404≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 9a1d7c5f0d82e8665715d5e47c9410c6a97e3748≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 5215ea00a747eca34cb2f603cfef91fef76c2558≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < cbcc0e8dea499e5ca86b583372ccb1815cccc570 and 2 more ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < a13cdb19fcb223ed41bdab3bab42b98dba87e90bversion 2.6.12	Vulnerable	CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 15, 2026 → Oct 26, 2026 · 11 reading(s) · max 0.20%

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.

application logs

Timeline

What happened to this CVE, newest first.

2026
Record published
Oct 15, 2026
Affected products added · linux/linux
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Sep 4, 2026 · Linux

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/a13cdb19fcb223ed41bdab3bab42b98dba87e90b
NIST National Vulnerability Database
git.kernel.org/stable/c/a38212687519f2a72f43e62dec1348a690412404
NIST National Vulnerability Database
git.kernel.org/stable/c/5215ea00a747eca34cb2f603cfef91fef76c2558
NIST National Vulnerability Database
git.kernel.org/stable/c/cbcc0e8dea499e5ca86b583372ccb1815cccc570
NIST National Vulnerability Database
github.com/advisories/GHSA-4wjj-fc9c-xhfj
GitHub Security Advisories
git.kernel.org/stable/c/465544b3d6602cfbdc2305d5cbfb7f4954353b63
NIST National Vulnerability Database
git.kernel.org/stable/c/9a1d7c5f0d82e8665715d5e47c9410c6a97e3748
NIST National Vulnerability Database
git.kernel.org/stable/c/c1d9c16af51cc6ff92a5a062617d3b022dd01078
NIST National Vulnerability Database
git.kernel.org/stable/c/4993e1ab85d7d3f4a40d81852170f9665483bbd8
NIST National Vulnerability Database
git.kernel.org/stable/c/313ead1abed945544703b100a12c5a10fdf78409
NIST National Vulnerability Database
nvd.nist.gov/vuln/detail/CVE-2026-80781
GitHub Security Advisories

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Unknown CVE-2026-99092 riscv: patch: fix handling of bpf-jit execmem addresses 1d
Unknown CVE-2026-99093 mm: don't schedule deferred kernel page table freeing while booting 1d
Unknown CVE-2026-99095 drm/vc4: drain the hangcheck timer and works on V3D unbind 1d
Unknown CVE-2026-99096 io_uring/register: don't exempt disabled rings from task restrictions 1d
Unknown CVE-2026-99097 tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper() 1d
Unknown CVE-2026-99098 dm-integrity: fix buffer overflow in inline mode with large tag size 1d

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-80781 is "HID: core: fix OOB read of field->usage in hid_set_field()", 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.20% 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.