{"id":"CVE-2024-56545","title":"HID: hyperv: streamline driver probe to avoid devres issues","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nHID: hyperv: streamline driver probe to avoid devres issues\n\nIt was found that unloading 'hid_hyperv' module results in a devres\ncomplaint:\n\n ...\n hv_vmbus: unregisteri…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= 62c68e7cee332e08e625af3bca3318814086490d < b03e713a400aeb5f969bab4daf47a7402d0df814","Linux >= 62c68e7cee332e08e625af3bca3318814086490d < 19a9457e5e210e408c1f8865b5d93c5a2c90409d","Linux >= 62c68e7cee332e08e625af3bca3318814086490d < 3d48d0fbaaa74a04fb9092780a3f83dc4f3f8160","Linux >= 62c68e7cee332e08e625af3bca3318814086490d < 66ef47faa90d838cda131fe1f7776456cc3b59f2","Linux e6ea3de7abef998aaab9f04a7a11a7c5f56bbe57","Linux ac0d8318082f549419104cfe9cb6a9deb2df9853","Linux 4d1617e40713a6202b6165ca137b09aaf35637f5","Linux >= 5.10.270 < 5.11","Linux >= 5.15.221 < 5.16","Linux >= 6.1.188 < 6.2","Linux 6.5"],"published":"2024-12-27","updated":"2026-09-14","sourceUpdated":"2026-09-14T11:57:48.267Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2024-56545","references":[{"url":"https://git.kernel.org/stable/c/b03e713a400aeb5f969bab4daf47a7402d0df814"},{"url":"https://git.kernel.org/stable/c/19a9457e5e210e408c1f8865b5d93c5a2c90409d"},{"url":"https://git.kernel.org/stable/c/3d48d0fbaaa74a04fb9092780a3f83dc4f3f8160"},{"url":"https://git.kernel.org/stable/c/66ef47faa90d838cda131fe1f7776456cc3b59f2"}],"tags":["cve.org"],"epss":0.00213,"epssPercentile":0.11939,"ingestedAt":"2026-09-14T15:23:07.460Z","slug":"CVE-2024-56545","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: hyperv: streamline driver probe to avoid devres issues\n\nIt was found that unloading 'hid_hyperv' module results in a devres\ncomplaint:\n\n ...\n hv_vmbus: unregistering driver hid_hyperv\n ------------[ cut here ]------------\n WARNING: CPU: 2 PID: 3983 at drivers/base/devres.c:691 devres_release_group+0x1f2/0x2c0\n ...\n Call Trace:\n  <TASK>\n  ? devres_release_group+0x1f2/0x2c0\n  ? __warn+0xd1/0x1c0\n  ? devres_release_group+0x1f2/0x2c0\n  ? report_bug+0x32a/0x3c0\n  ? handle_bug+0x53/0xa0\n  ? exc_invalid_op+0x18/0x50\n  ? asm_exc_invalid_op+0x1a/0x20\n  ? devres_release_group+0x1f2/0x2c0\n  ? devres_release_group+0x90/0x2c0\n  ? rcu_is_watching+0x15/0xb0\n  ? __pfx_devres_release_group+0x10/0x10\n  hid_device_remove+0xf5/0x220\n  device_release_driver_internal+0x371/0x540\n  ? klist_put+0xf3/0x170\n  bus_remove_device+0x1f1/0x3f0\n  device_del+0x33f/0x8c0\n  ? __pfx_device_del+0x10/0x10\n  ? cleanup_srcu_struct+0x337/0x500\n  hid_destroy_device+0xc8/0x130\n  mousevsc_remove+0xd2/0x1d0 [hid_hyperv]\n  device_release_driver_internal+0x371/0x540\n  driver_detach+0xc5/0x180\n  bus_remove_driver+0x11e/0x2a0\n  ? __mutex_unlock_slowpath+0x160/0x5e0\n  vmbus_driver_unregister+0x62/0x2b0 [hv_vmbus]\n  ...\n\nAnd the issue seems to be that the corresponding devres group is not\nallocated. Normally, devres_open_group() is called from\n__hid_device_probe() but Hyper-V HID driver overrides 'hid_dev->driver'\nwith 'mousevsc_hid_driver' stub and basically re-implements\n__hid_device_probe() by calling hid_parse() and hid_hw_start() but not\ndevres_open_group(). hid_device_probe() does not call __hid_device_probe()\nfor it. Later, when the driver is removed, hid_device_remove() calls\ndevres_release_group() as it doesn't check whether hdev->driver was\ninitially overridden or not.\n\nThe issue seems to be related to the commit 62c68e7cee33 (\"HID: ensure\ntimely release of driver-allocated resources\") but the commit itself seems\nto be correct.\n\nFix the issue by dropping the 'hid_dev->driver' override and using\nhid_register_driver()/hid_unregister_driver() instead. Alternatively, it\nwould have been possible to rely on the default handling but\nHID_CONNECT_DEFAULT implies HID_CONNECT_HIDRAW and it doesn't seem to work\nfor mousevsc as-is.\n\n## Affected\n\n- `Linux >= 62c68e7cee332e08e625af3bca3318814086490d < b03e713a400aeb5f969bab4daf47a7402d0df814`\n- `Linux >= 62c68e7cee332e08e625af3bca3318814086490d < 19a9457e5e210e408c1f8865b5d93c5a2c90409d`\n- `Linux >= 62c68e7cee332e08e625af3bca3318814086490d < 3d48d0fbaaa74a04fb9092780a3f83dc4f3f8160`\n- `Linux >= 62c68e7cee332e08e625af3bca3318814086490d < 66ef47faa90d838cda131fe1f7776456cc3b59f2`\n- `Linux e6ea3de7abef998aaab9f04a7a11a7c5f56bbe57`\n- `Linux ac0d8318082f549419104cfe9cb6a9deb2df9853`\n- `Linux 4d1617e40713a6202b6165ca137b09aaf35637f5`\n- `Linux >= 5.10.270 < 5.11`\n- `Linux >= 5.15.221 < 5.16`\n- `Linux >= 6.1.188 < 6.2`\n- `Linux 6.5`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[{"seq":202663,"id":"CVE-2024-56545","ts":1789402174340,"field":"cvss","old":"5.5","new":null},{"seq":202662,"id":"CVE-2024-56545","ts":1789402174340,"field":"severity","old":"medium","new":"none"}]}