{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80781 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80781 is a memory corruption vulnerability in Linux, published on 4 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-80781 and fix it if it is affected.\n\nWhat it is: CVE-2026-80781 is a memory corruption vulnerability in Linux, published on 4 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-80781 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-80781/ (Markdown: https://insights.sbomify.com/CVE-2026-80781/index.md)","id":"CVE-2026-80781","markdown":"https://insights.sbomify.com/CVE-2026-80781/index.md","name":"CVE-2026-80781","record":{"aliases":["AZL-99407","BELL-CVE-2026-80781","DEBIAN-CVE-2026-80781","GHSA-4wjj-fc9c-xhfj","UBUNTU-CVE-2026-80781"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"none","summary":"An out-of-bounds read in the Linux kernel HID subsystem allows local attackers to leak memory or crash the system when debugfs is enabled.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nHID: core: fix OOB read of field-\u003eusage in hid_set_field()\n\nhid_set_field() hands field-\u003eusage + offset to hid_dump_input() before\nthe guard that bounds offset:\n\n\thid_dump_input(field-\u003ereport-\u003edevice, field-\u003eusage + offset, value);\n\n\tif (offset \u003e= field-\u003ereport_count) {\n\t\thid_err(...);\n\t\treturn -1;\n\t}\n\nUnder CONFIG_DEBUG_FS hid_dump_input() dereferences that pointer, with\nbuf = hid_resolv_usage(usage-\u003ehid, NULL).  The usage[] array is\nallocated inline with the hid_field in hid_register_field() and holds\nfield-\u003emaxusage entries, so an offset past it reads off the end of the\nkvzalloc()ed allocation and into a neighbouring object.  Had the guard\nrun first, offset \u003c report_count \u003c= maxusage would already have confined\nthe pointer to the array.\n\nA caller supplies such an offset today.  picolcd_fb_send_tile()\nvalidates only report-\u003emaxfield before issuing\nhid_set_field(report-\u003efield[0], 11 + i, ...) for i = 0..31, so its\noffsets are fixed at 11..42 and are never checked against the bound\nfield.  When the device registers that field with fewer usages, the\nframebuffer deferred-io work drives the read on every tile.  KASAN\nreports a 4-byte slab-out-of-bounds read in hid_dump_input() below\nhid_set_field(), and the same boot logs \"offset (1) exceeds\nreport_count (1)\" from the guard that runs only afterwards.\n\nMove the hid_dump_input() call below the guard.  Because\nfield-\u003emaxusage \u003e= field-\u003ereport_count, the guard then establishes that\nfield-\u003eusage + offset lies inside the array before it is dereferenced,\nfor every caller and without changing behaviour on the valid path.\n\nDiscovered by XBOW, triaged by Baul Lee \u003cbaul.lee@xbow.com\u003e","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"HID: core: fix OOB read of field-\u003eusage in hid_set_field()","id":"CVE-2026-80781","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":9,"next":{"headline":"HID: magicmouse: do not keep a stale msc-\u003einput if no input is claimed","id":"CVE-2026-80782"},"packages":[],"prev":{"headline":"HID: pidff: fix OOB write when hid-\u003einputs is empty","id":"CVE-2026-80780"},"products":["Linux"],"published":"2026-09-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"An out-of-bounds read in the Linux kernel HID subsystem allows local attackers to leak memory or crash the system when debugfs is enabled.","url":"https://insights.sbomify.com/CVE-2026-80781/"}