CVE-2026-80765: HID: hyperv: validate initial device info bounds
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Fixed version: Linux Linux 2529737763cb4bcfcaf397beeea2664656c865b4, 334271d3812ab3197c95b4593bc6745f8d189114, 390d3d9c52a710fdc9de95a537747397c0c671d1; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 2529737763cb4bcfcaf397beeea2664656c865b4, 334271d3812ab3197c95b4593bc6745f8d189114, 390d3d9c52a710fdc9de95a537747397c0c671d1; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 4, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.3affected
- b95f5bcb811e3905b5376f87789da8d097fee682 and later · before e0d5d3e45e142b7ef7525654aaa54d3e986002a6affected · git
- b95f5bcb811e3905b5376f87789da8d097fee682 and later · before 390d3d9c52a710fdc9de95a537747397c0c671d1affected · git
- b95f5bcb811e3905b5376f87789da8d097fee682 and later · before 8614c043b11cc35ffebd35542ab4da275f8f923daffected · git
- b95f5bcb811e3905b5376f87789da8d097fee682 and later · before 334271d3812ab3197c95b4593bc6745f8d189114affected · git
- b95f5bcb811e3905b5376f87789da8d097fee682 and later · before f84d777574b748b1a488723ca7be9d87a301a872affected · git
- b95f5bcb811e3905b5376f87789da8d097fee682 and later · before 608f8fd8c0f7b6268da43509447802955f210aacaffected · git
- b95f5bcb811e3905b5376f87789da8d097fee682 and later · before 2529737763cb4bcfcaf397beeea2664656c865b4affected · git
- b95f5bcb811e3905b5376f87789da8d097fee682 and later · before c894143c508a7e063aab9f73c9e835ab40121283affected · git
- b95f5bcb811e3905b5376f87789da8d097fee682 and later · before 934b7778aa7b7c8f6bb073d2a73ba3674885bae0affected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.107-1 | 6.12.107-1 |
| Debian:14 | linux | before 7.1.12-1 | 7.1.12-1 |
| openSUSE:Tumbleweed | kernel-source | before 7.2.5-1.1 | 7.2.5-1.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80763Sep 4, 2026 · Bluetooth: hci_event: validate LE Set CIG Parameters response0Monitor
- ← EarlierCVE-2026-80764Sep 4, 2026 · Bluetooth: hci_event: fix LE list UAF on reset0Monitor
- Later →CVE-2026-80766Sep 4, 2026 · HID: uclogic: fix use-after-free of inrange_timer on remove0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2529737763cb4bcfcaf397beeea2664656c865b4 | Vendor (CNA) |
| Linux Linux | 334271d3812ab3197c95b4593bc6745f8d189114 | Vendor (CNA) |
| Linux Linux | 390d3d9c52a710fdc9de95a537747397c0c671d1 | Vendor (CNA) |
| Linux Linux | 608f8fd8c0f7b6268da43509447802955f210aac | Vendor (CNA) |
| Linux Linux | 8614c043b11cc35ffebd35542ab4da275f8f923d | Vendor (CNA) |
| Linux Linux | 934b7778aa7b7c8f6bb073d2a73ba3674885bae0 | Vendor (CNA) |
| Linux Linux | c894143c508a7e063aab9f73c9e835ab40121283 | Vendor (CNA) |
| Linux Linux | e0d5d3e45e142b7ef7525654aaa54d3e986002a6 | Vendor (CNA) |
| Linux Linux | f84d777574b748b1a488723ca7be9d87a301a872 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-source | 7.2.5-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/334271d3812ab3197c95b4593bc6745f8d189114
- git.kernel.org/stable/c/390d3d9c52a710fdc9de95a537747397c0c671d1
- git.kernel.org/stable/c/608f8fd8c0f7b6268da43509447802955f210aac
- git.kernel.org/stable/c/8614c043b11cc35ffebd35542ab4da275f8f923d
- git.kernel.org/stable/c/934b7778aa7b7c8f6bb073d2a73ba3674885bae0
- git.kernel.org/stable/c/c894143c508a7e063aab9f73c9e835ab40121283
- git.kernel.org/stable/c/e0d5d3e45e142b7ef7525654aaa54d3e986002a6
- git.kernel.org/stable/c/f84d777574b748b1a488723ca7be9d87a301a872
Vendor advisories and official records. Exploit/PoC links are deliberately left out.