Look up another CVE · open CVE-2026-80604 in the interactive tracker
CVE-2026-80604
HID: core: Fix OOB read in hid_get_report for numbered reports
Published 2026-08-28 (2 months ago) by the Linux kernel CNA. Subsystem drivers/hid. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-80604 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixed | 6.1.180-1 | Update the kernel and reboot. Fixed in 6.1.180-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixed | 6.12.100-1 | Update the kernel and reboot. Fixed in 6.12.100-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
When a caller passes a size of 0 to hid_report_raw_event() for a numbered report, the function originally called hid_get_report() before performing any size validation. Inside hid_get_report(), if the report is numbered (report_enum->numbered is true), it unconditionally dereferences data[0] to extract the report ID. With a size of 0, this results in an out-of-bounds read or kernel panic. Fix this by moving the numbered report size validation check before the call to hid_get_report(), ensuring that size is at least 1 before dereferencing the data pointer.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/hid/hid-core.c
- What this is
- HID CORE LAYERMAINTAINERS section matched on drivers/hid/ · linux-input@vger.kernel.org · Maintained
- Kernel module
- hid
Check it on the machine
grep -wE 'CONFIG_HID|CONFIG_HID_SUPPORT' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w hidPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.
- bookwormMnot built on arm64/cloud-arm64
- trixieBnot built on arm64/cloud-arm64
- forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64
- M
- a module where it is built at all; some flavours do not build it
- B
- built in on some, a module on others, absent on the rest
- Build switches
- CONFIG_HID, CONFIG_HID_SUPPORT
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-08-28 (2 months ago)source
- CVSS
- 8.8 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- adjacent network (AV:A)source
- EPSS
- 0.41%, higher than 34.0% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/hid
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 5.10.259 | 5.10.261 | f8896b684e24 |
| 5.15.210 | 5.15.212 | 30ff978af92c |
| 6.1.176 | 6.1.178 | c39f5765ad84 |
| 6.6.143 | 6.6.145 | c973d53bcd42 |
| 6.12.93 | 6.12.97 | c1fc0d3aff26 |
| 6.18.33 | 6.18.40 | dd395744e4ed |
| 7.1 | 7.1.5 | f7e8117e42b2 |
| 7.1 | 7.2 | af1a9b65ebe8 |
| 7.0.10 | 0 | 0 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:AAttack vector, adjacent network
- 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.
- AC:LAttack complexity, low
- 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.
- PR:NPrivileges required, none
- 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.
- UI:NUser interaction, none
- 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.
- S:UScope, unchanged
- 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.
- C:HConfidentiality impact, high
- 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.
- I:HIntegrity impact, high
- 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.
- A:HAvailability impact, high
- 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.