data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-80765 in the interactive tracker

CVE-2026-80765

HID: hyperv: validate initial device info bounds

EPSS 0.2%

Published 2026-09-04 (44 days 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-80765 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

ReleaseStatus VersionWhat this means
Debian 12bookwormfixedDLA-4777-1 · 2026-09-08 · text6.1.187-1Update the kernel and reboot. DLA-4777-1 shipped the fix on 2026-09-08, in 6.1.187-1. A running kernel keeps the old code until the machine restarts.
Debian 13trixiefixed6.12.107-1Update the kernel and reboot. Fixed in 6.12.107-1. A running kernel keeps the old code until the machine restarts.
Debian 14forkyfixed7.1.12-1Update the kernel and reboot. Fixed in 7.1.12-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed7.1.12-1Update the kernel and reboot. Fixed in 7.1.12-1. A running kernel keeps the old code until the machine restarts.
Debian 12bookworm · linux-6.12fixedDLA-4788-1 · 2026-09-19 · text6.12.107-1~deb12u1Update the kernel and reboot. DLA-4788-1 shipped the fix on 2026-09-19, in 6.12.107-1~deb12u1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

The Hyper-V synthetic HID host supplies SYNTH_HID_INITIAL_DEVICE_INFO messages that contain a HID descriptor followed by the report descriptor bytes. mousevsc_on_receive_device_info() trusts bLength and wDescriptorLength without checking that the received packet contains both byte ranges. A malformed host or backend message can therefore make the guest read past the received VMBus packet while copying the report descriptor. Pass the received initial-device-info size into the parser and reject descriptor lengths that exceed the packet. Impact: A malicious Hyper-V host or backend can crash a guest by sending a short initial device-info message with an oversized HID report descriptor length.

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-hyperv.c

What this is
Hyper-V/Azure CORE AND DRIVERSMAINTAINERS section matched on drivers/hid/hid-hyperv.c · linux-hyperv@vger.kernel.org · Supported
Kernel module
hid_hyperv

Check it on the machine

grep -wE 'CONFIG_HID|CONFIG_HID_HYPERV_MOUSE|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 hid_hyperv

Prints 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, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le
  • trixieMnot built on arm64/cloud-arm64, armel/rpi, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
  • forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armhf/armmp, armhf/armmp-lpae, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
  • bookworm · linux-6.12Mnot built on arm64/cloud-arm64, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le, ppc64el/powerpc64le-64k
M
a module where it is built at all; some flavours do not build it
Build switches
CONFIG_HID, CONFIG_HID_HYPERV_MOUSE, 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-09-04 (44 days ago)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
0.19%, higher than 8.6% 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

IntroducedFixed inCommit
3.35.10.267e0d5d3e45e14
3.35.15.218390d3d9c52a7
3.36.1.1858614c043b11c
3.36.6.154334271d3812a
3.36.12.106f84d777574b7
3.36.18.47608f8fd8c0f7
3.37.1.112529737763cb
3.37.2.1c894143c508a
3.37.3934b7778aa7b

Debian advisories

AdvisoryDateShipped toDebian
DLA-4788-12026-09-19bookworm 6.12.107-1~deb12u1tracker
DLA-4777-12026-09-08bookworm 6.1.187-1tracker

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2026-80765, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.