Look up another CVE · open CVE-2026-64367 in the interactive tracker
CVE-2026-64367
HID: hid-goodix-spi: validate report size to prevent stack buffer overflow
Published 2026-07-25 (3 months ago) by the Linux kernel CNA. Subsystem drivers/hid. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-64367 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 | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | fixed | 6.12.96-1 | Update the kernel and reboot. Fixed in 6.12.96-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.1.4-1 | Update the kernel and reboot. Fixed in 7.1.4-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.4-1 | Update the kernel and reboot. Fixed in 7.1.4-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4724-1 · 2026-08-07 · text | 6.12.100-1~deb12u1 | Update the kernel and reboot. DLA-4724-1 shipped the fix on 2026-08-07, in 6.12.100-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
goodix_hid_set_raw_report() builds a protocol frame in a 128-byte stack buffer (tmp_buf), writing an 11-12 byte header followed by the caller-supplied report data. The HID core caps report size at HID_MAX_BUFFER_SIZE (16384) by default, while the driver does not set hid_ll_driver.max_buffer_size and performs no bounds checking before copying the payload: memcpy(tmp_buf + tx_len, buf, len); A hidraw SET_REPORT ioctl with a report larger than ~116 bytes overflows the stack buffer. Add a size check after constructing the header, rejecting reports that would exceed the buffer capacity. Discovered by Atuin - Automated Vulnerability Discovery Engine.
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-goodix-spi.c
- What this is
- HID CORE LAYERMAINTAINERS section matched on drivers/hid/ · linux-input@vger.kernel.org · Maintained
Check it on the machine
grep -wE 'CONFIG_HID_GOODIX_SPI|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.
Show whether Debian builds this, per release
Debian does not build this code in 4 releases. The build rule could not be established for 1 release, so nothing is claimed about those.
- bookworm?
- trixie, forky, sid, bookworm · linux-6.12n
- ?
- not established - no Makefile entry for the affected file
- n
- not enabled on any flavour - this release does not build the code
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
- Build switches
- CONFIG_HID_GOODIX_SPI, 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-07-25 (3 months ago)source
- CVSS
- 7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.14%, higher than 3.2% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- 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 |
|---|---|---|
| 6.12 | 6.12.96 | ad47ad624f2f |
| 6.12 | 6.18.39 | dae1d000ddfd |
| 6.12 | 7.1.4 | 835fcc865556 |
| 6.12 | 7.2 | db0a0768d092 |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4724-1 | 2026-08-07 | bookworm 6.12.100-1~deb12u1 | tracker |
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:LAttack vector, local
- An attacker reaches the flaw locally through a SET_REPORT operation on the Goodix touchscreen's /dev/hidraw device.
- AC:LAttack complexity, low
- A single attacker-controlled report exceeding the 116-117 byte safe payload limit deterministically triggers the overwrite, with no race or external condition required.
- PR:LPrivileges required, low
- The kernel path has no capability or namespace checks; an unprivileged user granted access to the hidraw node can trigger it.
- UI:NUser interaction, none
- No victim action is required once the attacker can access the device node.
- S:UScope, unchanged
- Any privilege escalation or kernel compromise remains within the host kernel's security authority.
- C:HConfidentiality impact, high
- The attacker-controlled stack overwrite can corrupt control data and enable kernel code execution, thereby exposing arbitrary kernel memory.
- I:HIntegrity impact, high
- The attacker can overwrite far beyond the 128-byte stack buffer with controlled data, potentially hijacking control flow and modifying arbitrary kernel state.
- A:HAvailability impact, high
- The overflow can reliably trigger stack-canary failure, kernel oops, or panic, and can be repeated through additional SET_REPORT requests.