CVE-2026-80765

HID: hyperv: validate initial device info bounds

N/A
Published: September 4, 2026 at 03:12 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: HID: hyperv: validate initial device info bounds 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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.3b95f5bcb811e3905b5376f87789da8d097fee682
Vendor states this is fixed in 2529737763cb4bcfcaf397beeea2664656c865b4 (fixed)
Vendor states this is fixed in 334271d3812ab3197c95b4593bc6745f8d189114 (fixed)
Vendor states this is fixed in 390d3d9c52a710fdc9de95a537747397c0c671d1 (fixed)
Vendor states this is fixed in 608f8fd8c0f7b6268da43509447802955f210aac (fixed)
Vendor states this is fixed in 8614c043b11cc35ffebd35542ab4da275f8f923d (fixed)
Vendor states this is fixed in 934b7778aa7b7c8f6bb073d2a73ba3674885bae0 (fixed)
Vendor states this is fixed in c894143c508a7e063aab9f73c9e835ab40121283 (fixed)
Vendor states this is fixed in e0d5d3e45e142b7ef7525654aaa54d3e986002a6 (fixed)
Vendor states this is fixed in f84d777574b748b1a488723ca7be9d87a301a872 (fixed)
Vendor states this is fixed in 3.3 (unaffected)
Vendor states this is fixed in 5.10.267 (unaffected)
Vendor states this is fixed in 5.15.218 (unaffected)
Vendor states this is fixed in 6.1.185 (unaffected)
Vendor states this is fixed in 6.12.106 (unaffected)
Vendor states this is fixed in 6.18.47 (unaffected)
Vendor states this is fixed in 6.6.154 (unaffected)
Vendor states this is fixed in 7.1.11 (unaffected)
Vendor states this is fixed in 7.2.1 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card