HID: hyperv: streamline driver probe to avoid devres issues
Noroxi assessment
Priority: Monitor (action score 22/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.21% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 19a9457e5e210e408c1f8865b5d93c5a2c90409d, 3d48d0fbaaa74a04fb9092780a3f83dc4f3f8160, 4c419126cf71ca1f358ec0b8ccc448928719d502.
Low priority for now. Upgrade to Linux Linux 19a9457e5e210e408c1f8865b5d93c5a2c90409d, 3d48d0fbaaa74a04fb9092780a3f83dc4f3f8160, 4c419126cf71ca1f358ec0b8ccc448928719d502 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: streamline driver probe to avoid devres issues It was found that unloading 'hid_hyperv' module results in a devres complaint: ... hv_vmbus: unregistering driver hid_hyperv ------------[ cut here ]------------ WARNING: CPU: 2 PID: 3983 at drivers/base/devres.c:691 devres_release_group+0x1f2/0x2c0 ... Call Trace: <TASK> ? devres_release_group+0x1f2/0x2c0 ? __warn+0xd1/0x1c0 ? devres_release_group+0x1f2/0x2c0 ? report_bug+0x32a/0x3c0 ? handle_bug+0x53/0xa0 ? exc_invalid_op+0x18/0x50 ? asm_exc_invalid_op+0x1a/0x20 ? devres_release_group+0x1f2/0x2c0 ? devres_release_group+0x90/0x2c0 ? rcu_is_watching+0x15/0xb0 ? __pfx_devres_release_group+0x10/0x10 hid_device_remove+0xf5/0x220 device_release_driver_internal+0x371/0x540 ? klist_put+0xf3/0x170 bus_remove_device+0x1f1/0x3f0 device_del+0x33f/0x8c0 ? __pfx_device_del+0x10/0x10 ? cleanup_srcu_struct+0x337/0x500 hid_destroy_device+0xc8/0x130 mousevsc_remove+0xd2/0x1d0 [hid_hyperv] device_release_driver_internal+0x371/0x540 driver_detach+0xc5/0x180 bus_remove_driver+0x11e/0x2a0 ? __mutex_unlock_slowpath+0x160/0x5e0 vmbus_driver_unregister+0x62/0x2b0 [hv_vmbus] ... And the issue seems to be that the corresponding devres group is not allocated. Normally, devres_open_group() is called from __hid_device_probe() but Hyper-V HID driver overrides 'hid_dev->driver' with 'mousevsc_hid_driver' stub and basically re-implements __hid_device_probe() by calling hid_parse() and hid_hw_start() but not devres_open_group(). hid_device_probe() does not call __hid_device_probe() for it. Later, when the driver is removed, hid_device_remove() calls devres_release_group() as it doesn't check whether hdev->driver was initially overridden or not. The issue seems to be related to the commit 62c68e7cee33 ("HID: ensure timely release of driver-allocated resources") but the commit itself seems to be correct. Fix the issue by dropping the 'hid_dev->driver' override and using hid_register_driver()/hid_unregister_driver() instead. Alternatively, it would have been possible to rely on the default handling but HID_CONNECT_DEFAULT implies HID_CONNECT_HIDRAW and it doesn't seem to work for mousevsc as-is.
- Published
- Dec 27, 2024
- Updated
- Oct 3, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.5 and later · before 6.6.64
- linux linux kernel6.7 and later · before 6.11.11
- linux linux kernel6.12 and later · before 6.12.2
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
- 6.5affected
- e6ea3de7abef998aaab9f04a7a11a7c5f56bbe57 and later · before b7c074d21fe8a8ee3b4f866a12c72cad6a5826ebaffected · git
- ac0d8318082f549419104cfe9cb6a9deb2df9853 and later · before 4c419126cf71ca1f358ec0b8ccc448928719d502affected · git
- 4d1617e40713a6202b6165ca137b09aaf35637f5 and later · before a216f6dc0444c3bd900bca66b9f21467d08e3ed3affected · git
- 62c68e7cee332e08e625af3bca3318814086490d and later · before b03e713a400aeb5f969bab4daf47a7402d0df814affected · git
- 62c68e7cee332e08e625af3bca3318814086490d and later · before 19a9457e5e210e408c1f8865b5d93c5a2c90409daffected · git
- 62c68e7cee332e08e625af3bca3318814086490d and later · before 3d48d0fbaaa74a04fb9092780a3f83dc4f3f8160affected · git
- 62c68e7cee332e08e625af3bca3318814086490d and later · before 66ef47faa90d838cda131fe1f7776456cc3b59f2affected · git
- 5.10.270 and later · before 5.10.271affected · semver
- 5.15.221 and later · before 5.15.222affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.3-1 | 6.12.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
- CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV77This week
- CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV77This week
- CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV77This week
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 | 19a9457e5e210e408c1f8865b5d93c5a2c90409d | Vendor (CNA) |
| Linux Linux | 3d48d0fbaaa74a04fb9092780a3f83dc4f3f8160 | Vendor (CNA) |
| Linux Linux | 4c419126cf71ca1f358ec0b8ccc448928719d502 | Vendor (CNA) |
| Linux Linux | 5.10.271 | Vendor (CNA) |
| Linux Linux | 5.15.222 | Vendor (CNA) |
| Linux Linux | 6.1.189 | Vendor (CNA) |
| Linux Linux | 66ef47faa90d838cda131fe1f7776456cc3b59f2 | Vendor (CNA) |
| Linux Linux | a216f6dc0444c3bd900bca66b9f21467d08e3ed3 | Vendor (CNA) |
| Linux Linux | b03e713a400aeb5f969bab4daf47a7402d0df814 | Vendor (CNA) |
| Linux Linux | b7c074d21fe8a8ee3b4f866a12c72cad6a5826eb | Vendor (CNA) |
| debian:linux | 6.12.3-1 · Debian:13 | 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
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
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 (6 more)Show less
- git.kernel.org/stable/c/3d48d0fbaaa74a04fb9092780a3f83dc4f3f8160
- git.kernel.org/stable/c/4c419126cf71ca1f358ec0b8ccc448928719d502
- git.kernel.org/stable/c/66ef47faa90d838cda131fe1f7776456cc3b59f2
- git.kernel.org/stable/c/a216f6dc0444c3bd900bca66b9f21467d08e3ed3
- git.kernel.org/stable/c/b03e713a400aeb5f969bab4daf47a7402d0df814
- git.kernel.org/stable/c/b7c074d21fe8a8ee3b4f866a12c72cad6a5826eb
Vendor advisories and official records. Exploit/PoC links are deliberately left out.