From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80765: HID: hyperv: validate initial device info bounds
Date: Fri, 4 Sep 2026 17:11:04 +0200 [thread overview]
Message-ID: <2026090400-CVE-2026-80765-9e7e@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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.
The Linux kernel CVE team has assigned CVE-2026-80765 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.3 with commit b95f5bcb811e3905b5376f87789da8d097fee682 and fixed in 5.10.267 with commit e0d5d3e45e142b7ef7525654aaa54d3e986002a6
Issue introduced in 3.3 with commit b95f5bcb811e3905b5376f87789da8d097fee682 and fixed in 5.15.218 with commit 390d3d9c52a710fdc9de95a537747397c0c671d1
Issue introduced in 3.3 with commit b95f5bcb811e3905b5376f87789da8d097fee682 and fixed in 6.1.185 with commit 8614c043b11cc35ffebd35542ab4da275f8f923d
Issue introduced in 3.3 with commit b95f5bcb811e3905b5376f87789da8d097fee682 and fixed in 6.6.154 with commit 334271d3812ab3197c95b4593bc6745f8d189114
Issue introduced in 3.3 with commit b95f5bcb811e3905b5376f87789da8d097fee682 and fixed in 6.12.106 with commit f84d777574b748b1a488723ca7be9d87a301a872
Issue introduced in 3.3 with commit b95f5bcb811e3905b5376f87789da8d097fee682 and fixed in 6.18.47 with commit 608f8fd8c0f7b6268da43509447802955f210aac
Issue introduced in 3.3 with commit b95f5bcb811e3905b5376f87789da8d097fee682 and fixed in 7.1.11 with commit 2529737763cb4bcfcaf397beeea2664656c865b4
Issue introduced in 3.3 with commit b95f5bcb811e3905b5376f87789da8d097fee682 and fixed in 7.2.1 with commit c894143c508a7e063aab9f73c9e835ab40121283
Issue introduced in 3.3 with commit b95f5bcb811e3905b5376f87789da8d097fee682 and fixed in 7.3-rc1 with commit 934b7778aa7b7c8f6bb073d2a73ba3674885bae0
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-80765
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/hid/hid-hyperv.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/e0d5d3e45e142b7ef7525654aaa54d3e986002a6
https://git.kernel.org/stable/c/390d3d9c52a710fdc9de95a537747397c0c671d1
https://git.kernel.org/stable/c/8614c043b11cc35ffebd35542ab4da275f8f923d
https://git.kernel.org/stable/c/334271d3812ab3197c95b4593bc6745f8d189114
https://git.kernel.org/stable/c/f84d777574b748b1a488723ca7be9d87a301a872
https://git.kernel.org/stable/c/608f8fd8c0f7b6268da43509447802955f210aac
https://git.kernel.org/stable/c/2529737763cb4bcfcaf397beeea2664656c865b4
https://git.kernel.org/stable/c/c894143c508a7e063aab9f73c9e835ab40121283
https://git.kernel.org/stable/c/934b7778aa7b7c8f6bb073d2a73ba3674885bae0
reply other threads:[~2026-09-04 15:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026090400-CVE-2026-80765-9e7e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.