CVE-2026-80765 — HID: hyperv: validate initial device info bounds
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ b95f5bcb811e3905b5376f87789da8d097fee682 and < e0d5d3e45e142b7ef7525654aaa54d3e986002a6≥ b95f5bcb811e3905b5376f87789da8d097fee682 and < 390d3d9c52a710fdc9de95a537747397c0c671d1≥ b95f5bcb811e3905b5376f87789da8d097fee682 and < 8614c043b11cc35ffebd35542ab4da275f8f923d≥ b95f5bcb811e3905b5376f87789da8d097fee682 and < 334271d3812ab3197c95b4593bc6745f8d189114≥ b95f5bcb811e3905b5376f87789da8d097fee682 and < f84d777574b748b1a488723ca7be9d87a301a872≥ b95f5bcb811e3905b5376f87789da8d097fee682 and < 608f8fd8c0f7b6268da43509447802955f210aac≥ b95f5bcb811e3905b5376f87789da8d097fee682 and < 2529737763cb4bcfcaf397beeea2664656c865b4≥ b95f5bcb811e3905b5376f87789da8d097fee682 and < c894143c508a7e063aab9f73c9e835ab40121283 and 2 more≥ b95f5bcb811e3905b5376f87789da8d097fee682 and < 934b7778aa7b7c8f6bb073d2a73ba3674885bae0version 3.3 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 28, 2026 · 13 reading(s) · max 0.20%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
11 on the record
- git.kernel.org/stable/c/f84d777574b748b1a488723ca7be9d87a301a872
- nvd.nist.gov/vuln/detail/CVE-2026-80765
- git.kernel.org/stable/c/334271d3812ab3197c95b4593bc6745f8d189114
- git.kernel.org/stable/c/608f8fd8c0f7b6268da43509447802955f210aac
- git.kernel.org/stable/c/934b7778aa7b7c8f6bb073d2a73ba3674885bae0
- git.kernel.org/stable/c/e0d5d3e45e142b7ef7525654aaa54d3e986002a6
- git.kernel.org/stable/c/390d3d9c52a710fdc9de95a537747397c0c671d1
- git.kernel.org/stable/c/c894143c508a7e063aab9f73c9e835ab40121283
- git.kernel.org/stable/c/8614c043b11cc35ffebd35542ab4da275f8f923d
- git.kernel.org/stable/c/2529737763cb4bcfcaf397beeea2664656c865b4
- github.com/advisories/GHSA-cj68-x55r-245c
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 1d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 1d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 1d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 1d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 1d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-80765 is "HID: hyperv: validate initial device info bounds", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.20% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.