In the Linux kernel, the following vulnerability has been resolved:
HID: bpf: abort dispatch if device destroyed
The current HID bpf implementation assumes no output report/request will go through it after hid_bpf_destroy_device() has been called. This leads to a bug that unplugging certain types of HID devices causes a cleaned- up SRCU to be accessed. The bug was previously a hidden failure until a recent x86 percpu change [1] made it access not-present pages.
The bug will be triggered if the conditions below are met:
A) a device under the driver has some LEDs on B) hid_ll_driver->request() is uninplemented (e.g., logitech-djreceiver)
If condition A is met, hidinput_led_worker() is always scheduled *after* hid_bpf_destroy_device().
hid_destroy_device ` hid_bpf_destroy_device ` cleanup_srcu_struct(&hdev->bpf.srcu) ` hid_remove_device ` ... ` led_classdev_unregister ` led_trigger_set(led_cdev, NULL) ` led_set_brightness(led_cdev, LED_OFF) ` ... ` input_inject_event ` input_event_dispose ` hidinput_input_event ` schedule_work(&hid->led_work) [hidinput_led_worker]
This is fine when condition B is not met, where hidinput_led_worker() calls hid_ll_driver->request(). This is the case for most HID drivers, which implement it or use the generic one from usbhid. The driver itself or an underlying driver will then abort processing the request.
Otherwise, hidinput_led_worker() tries hid_hw_output_report() and leads to the bug.
hidinput_led_worker ` hid_hw_output_report ` dispatch_hid_bpf_output_report ` srcu_read_lock(&hdev->bpf.srcu) ` srcu_read_unlock(&hdev->bpf.srcu, idx)
The bug has existed since the introduction [2] of dispatch_hid_bpf_output_report(). However, the same bug also exists in dispatch_hid_bpf_raw_requests(), and I've reproduced (no visible effect because of the lack of [1], but confirmed bpf.destroyed == 1) the bug against the commit (i.e., the Fixes:) introducing the function. This is because hidinput_led_worker() falls back to hid_hw_raw_request() when hid_ll_driver->output_report() is uninplemented (e.g., logitech- djreceiver).
hidinput_led_worker ` hid_hw_output_report: -ENOSYS ` hid_hw_raw_request ` dispatch_hid_bpf_raw_requests ` srcu_read_lock(&hdev->bpf.srcu) ` srcu_read_unlock(&hdev->bpf.srcu, idx)
Fix the issue by returning early in the two mentioned functions if hid_bpf has been marked as destroyed. Though dispatch_hid_bpf_device_event() handles input events, and there is no evidence that it may be called after the destruction, the same check, as a safety net, is also added to it to maintain the consistency among all dispatch functions.
The impact of the bug on other architectures is unclear. Even if it acts as a hidden failure, this is still dangerous because it corrupts whatever is on the address calculated by SRCU. Thus, CC'ing the stable list.
[1]: commit 9d7de2aa8b41 ("x86/percpu/64: Use relative percpu offsets") [2]: commit 9286675a2aed ("HID: bpf: add HID-BPF hooks for hid_hw_output_report")
CVSS Details
- CVSS 3.1 Base Score: 8.8
- CVSS 3.1 Vector: (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
Covered by Rapid7
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Amazon_linux_2023 | — | Upgrade kernel-libbpf-debuginfoUpgrade kernel6.12-debuginfo-common-x86_64Upgrade kernel-tools-debuginfoUpgrade kernel-livepatch-6.12.30-34.92Upgrade perf6.12-debuginfoUpgrade kernel-libbpf-staticUpgrade bpftool-debuginfoUpgrade kernel-develUpgrade kernel-libbpfUpgrade kernel-tools-develUpgrade kernel-libbpf-develUpgrade bpftoolUpgrade python3-perf6.12Upgrade kernel-headersUpgrade python3-perf6.12-debuginfoUpgrade kernel-toolsUpgrade perf6.12Upgrade kernel6.12-debuginfoUpgrade kernel6.12-debuginfo-common-aarch64Upgrade kernel-modules-extra-commonUpgrade kernel6.12-modules-extraUpgrade kernel6.12 | Jul 11, 2025 | Jun 18, 2025 |
| Debian | — | Upgrade linux | Jul 23, 2026 | Jul 23, 2026 |
| Redhat_linux | — | No solution exists | Jul 9, 2025 | Jun 18, 2025 |
| Suse | — | Upgrade kernel-64kb-develUpgrade kernel-source-vanillaUpgrade kernel-docs-htmlUpgrade kernel-default-livepatchUpgrade kernel-azureUpgrade kernel-defaultUpgrade kernel-azure-extraUpgrade kernel-develUpgrade kernel-64kb-extraUpgrade kernel-default-vdsoUpgrade kernel-source-azureUpgrade kernel-kvmsmallUpgrade kernel-kvmsmall-vdsoUpgrade kernel-64kbUpgrade kernel-macrosUpgrade kernel-docsUpgrade kernel-obs-qaUpgrade kernel-kvmsmall-develUpgrade kernel-devel-azureUpgrade kernel-azure-develUpgrade kernel-default-extraUpgrade kernel-symsUpgrade kernel-azure-vdsoUpgrade kernel-default-develUpgrade kernel-sourceUpgrade kernel-zfcpdump | Dec 5, 2025 | Dec 5, 2025 |
| Ubuntu | — | Upgrade linux-image-6.14.0-28-generic-64kUpgrade linux-image-6.14.0-1010-azureUpgrade linux-image-aws-64kUpgrade linux-image-oracleUpgrade linux-image-virtual-6.14Upgrade linux-image-realtimeUpgrade linux-image-6.14.0-28-genericUpgrade linux-image-6.14.0-1011-aws-64kUpgrade linux-image-6.14.0-1011-awsUpgrade linux-image-genericUpgrade linux-image-oem-24.04Upgrade linux-image-azure-6.14Upgrade linux-image-6.14.0-1010-realtimeUpgrade linux-image-gcpUpgrade linux-image-virtualUpgrade linux-image-oem-6.14Upgrade linux-image-6.14.0-1014-gcp-64kUpgrade linux-image-oracle-64kUpgrade linux-image-virtual-hwe-24.04Upgrade linux-image-aws-64k-6.14Upgrade linux-image-generic-64kUpgrade linux-image-gcp-6.14Upgrade linux-image-generic-64k-6.14Upgrade linux-image-generic-hwe-24.04Upgrade linux-image-6.14.0-1011-oracleUpgrade linux-image-oem-24.04aUpgrade linux-image-generic-64k-hwe-24.04Upgrade linux-image-gcp-64k-6.14Upgrade linux-image-6.14.0-1014-gcpUpgrade linux-image-6.14.0-1010-oemUpgrade linux-image-generic-6.14Upgrade linux-image-gcp-64kUpgrade linux-image-raspiUpgrade linux-image-awsUpgrade linux-image-6.14.0-1012-raspiUpgrade linux-image-realtime-6.14Upgrade linux-image-azureUpgrade linux-image-oem-24.04cUpgrade linux-image-aws-6.14Upgrade linux-image-oracle-6.14Upgrade linux-image-raspi-6.14Upgrade linux-image-6.14.0-1011-oracle-64kUpgrade linux-image-oracle-64k-6.14 | Jun 26, 2025 | Jun 18, 2025 |
Prioritise with Active Threat Intelligence
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub