{ "schema_version": "1.6.1", "id": "RPI-CVE-2026-80604", "modified": "2026-10-09T11:39:44Z", "upstream": [ "CVE-2026-80604" ], "published": "2026-08-28T06:50:33Z", "summary": "HID: core: Fix OOB read in hid_get_report for numbered reports", "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nHID: core: Fix OOB read in hid_get_report for numbered reports\n\nWhen a caller passes a size of 0 to hid_report_raw_event() for a\nnumbered report, the function originally called hid_get_report() before\nperforming any size validation.\n\nInside hid_get_report(), if the report is numbered (report_enum->numbered\nis true), it unconditionally dereferences data[0] to extract the report ID.\nWith a size of 0, this results in an out-of-bounds read or kernel panic.\n\nFix this by moving the numbered report size validation check before the\ncall to hid_get_report(), ensuring that size is at least 1 before\ndereferencing the data pointer.", "severity": [ { "type": "CVSS_V3", "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H" } ], "affected": [ { "package": { "ecosystem": "Raspberry Pi OS:12", "name": "linux" }, "versions": [ "1:6.12.93-1+rpt1", "1:6.12.96-1+rpt1" ], "ecosystem_specific": { "binaries": [ { "binary_name": "linux-image-6.12.93+rpt-rpi-2712", "binary_version": "1:6.12.93-1+rpt1" }, { "binary_name": "linux-image-6.12.93+rpt-rpi-v6", "binary_version": "1:6.12.93-1+rpt1" }, { "binary_name": "linux-image-6.12.93+rpt-rpi-v7", "binary_version": "1:6.12.93-1+rpt1" }, { "binary_name": "linux-image-6.12.93+rpt-rpi-v7l", "binary_version": "1:6.12.93-1+rpt1" }, { "binary_name": "linux-image-6.12.93+rpt-rpi-v8", "binary_version": "1:6.12.93-1+rpt1" }, { "binary_name": "linux-image-6.12.93+rpt-rpi-v8-rt", "binary_version": "1:6.12.93-1+rpt1" }, { "binary_name": "linux-image-6.12.96+rpt-rpi-2712", "binary_version": "1:6.12.96-1+rpt1" }, { "binary_name": "linux-image-6.12.96+rpt-rpi-v6", "binary_version": "1:6.12.96-1+rpt1" }, { "binary_name": "linux-image-6.12.96+rpt-rpi-v7", "binary_version": "1:6.12.96-1+rpt1" }, { "binary_name": "linux-image-6.12.96+rpt-rpi-v7l", "binary_version": "1:6.12.96-1+rpt1" }, { "binary_name": "linux-image-6.12.96+rpt-rpi-v8", "binary_version": "1:6.12.96-1+rpt1" }, { "binary_name": "linux-image-6.12.96+rpt-rpi-v8-rt", "binary_version": "1:6.12.96-1+rpt1" } ] }, "database_specific": { "per_version": { "1:6.12.93-1+rpt1": { "linux_commit": "d8ab4e908235da7727f22dd36ad5af224671677d", "upstream_version": "6.12.93", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.12.97" }, "1:6.12.96-1+rpt1": { "linux_commit": "ae161617d7a4552fa91d03626b8d9f3696d17481", "upstream_version": "6.12.96", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.12.97" } } } }, { "package": { "ecosystem": "Raspberry Pi OS:13", "name": "linux" }, "versions": [ "1:6.18.33-1+rpt1", "1:6.18.34-1+rpt1", "1:6.18.39-1+rpt1" ], "ecosystem_specific": { "binaries": [ { "binary_name": "linux-image-6.18.33+rpt-rpi-2712", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-v6", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-v7", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-v8", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-v8-rt", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.34+rpt-rpi-2712", "binary_version": "1:6.18.34-1+rpt1" }, { "binary_name": "linux-image-6.18.34+rpt-rpi-v6", "binary_version": "1:6.18.34-1+rpt1" }, { "binary_name": "linux-image-6.18.34+rpt-rpi-v7", "binary_version": "1:6.18.34-1+rpt1" }, { "binary_name": "linux-image-6.18.34+rpt-rpi-v8", "binary_version": "1:6.18.34-1+rpt1" }, { "binary_name": "linux-image-6.18.34+rpt-rpi-v8-rt", "binary_version": "1:6.18.34-1+rpt1" }, { "binary_name": "linux-image-6.18.39+rpt-rpi-2712", "binary_version": "1:6.18.39-1+rpt1" }, { "binary_name": "linux-image-6.18.39+rpt-rpi-v6", "binary_version": "1:6.18.39-1+rpt1" }, { "binary_name": "linux-image-6.18.39+rpt-rpi-v7", "binary_version": "1:6.18.39-1+rpt1" }, { "binary_name": "linux-image-6.18.39+rpt-rpi-v8", "binary_version": "1:6.18.39-1+rpt1" }, { "binary_name": "linux-image-6.18.39+rpt-rpi-v8-rt", "binary_version": "1:6.18.39-1+rpt1" } ] }, "database_specific": { "per_version": { "1:6.18.33-1+rpt1": { "linux_commit": "95b85bebbedcaedfa7ca79116ed38b7376fba412", "upstream_version": "6.18.33", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.18.40" }, "1:6.18.34-1+rpt1": { "linux_commit": "c8c7494100e99ee05b11aaa4f0588a223a63d1af", "upstream_version": "6.18.34", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.18.40" }, "1:6.18.39-1+rpt1": { "linux_commit": "60ea684a8ace97bb0db1a16e20753bdd6ab371ff", "upstream_version": "6.18.39", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.18.40" } } } } ], "references": [ { "type": "ADVISORY", "url": "https://www.cve.org/CVERecord?id=CVE-2026-80604" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/f8896b684e246f3f00f45ba2b6803ae59b9cc768" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/30ff978af92cb51c9ba99f96fc4f4ac80d7001ba" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/c39f5765ad840b71ff8db812d0210f216cca96e4" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/c973d53bcd420b58c4a34c68198746286d77e9fa" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/c1fc0d3aff26ec9ff885b3e4c92eba98cf349678" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/dd395744e4ed87956fcbf81ecc6a20c51e35fa4e" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/f7e8117e42b20c30d2a5edab82c944a5e381d791" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/af1a9b65ebe8a948eda805c14b78d4d0767cb1b5" } ], "database_specific": { "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git", "upstream_modified": "2026-08-29T06:25:05Z", "severity": { "source": "kernel CNA", "cvss_v3_score": 8.8, "cvss_v3_severity": "High", "scenario": "AV:A - A malicious Bluetooth HID peripheral with numbered reports can reach hid_report_raw_event() during driver probe/feature mapping (e.g., mt_get_feature()) when hid_report_len() is 0, bypassing __hid_input_report(); BT HIDP delivers attacker-controlled descriptors over an adjacent wireless link.\nAC:L - An attacker fully controls the HID report descriptor and GET_REPORT responses; pairing/connecting a device with numbered reports plus a zero-length report ID 0 deterministically calls hid_report_raw_event() with size 0 during probe, with no race or victim-specific heap layout required.\nPR:N - Exploitation requires only a malicious HID peripheral presenting a crafted numbered-report descriptor; the attacker needs no local account, capabilities, or init-namespace privileges on the victim host.\nUI:N - Feature-mapping probe I/O runs automatically during HID enumeration when the device connects or auto-reconnects; no additional victim file-open, mount, or application interaction is needed beyond standard peripheral attachment handled by the kernel.\nS:U - The out-of-bounds read and kernel panic occur entirely within host kernel HID-core processing; impact does not cross a VM, container, or IOMMU boundary to a separate security authority.\nC:H - On numbered-report devices, hid_get_report() dereferences data[0] before any size validation when size is 0, causing an out-of-bounds kernel memory read that may disclose adjacent heap or slab contents.\nI:H - Kernel heap out-of-bounds reads in HID-core can corrupt parser state or be chained with further memory corruption primitives; per kernel guidance, OOB reads in kernel context warrant High integrity impact when exploitation potential exists.\nA:H - The fix commit and CVE description state that dereferencing data[0] with size 0 on numbered reports can cause a kernel panic; this is a kernel oops-class failure denying system availability until reboot." } } }