{ "dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": { "cveId": "CVE-2025-38016", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2025-04-16T04:51:23.977Z", "datePublished": "2025-06-18T09:28:24.883Z", "dateUpdated": "2026-08-05T11:58:58.847Z" }, "containers": { "cna": { "providerMetadata": { "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-08-05T11:58:58.847Z" }, "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nHID: bpf: abort dispatch if device destroyed\n\nThe current HID bpf implementation assumes no output report/request will\ngo through it after hid_bpf_destroy_device() has been called. This leads\nto a bug that unplugging certain types of HID devices causes a cleaned-\nup SRCU to be accessed. The bug was previously a hidden failure until a\nrecent x86 percpu change [1] made it access not-present pages.\n\nThe bug will be triggered if the conditions below are met:\n\nA) a device under the driver has some LEDs on\nB) hid_ll_driver->request() is uninplemented (e.g., logitech-djreceiver)\n\nIf condition A is met, hidinput_led_worker() is always scheduled *after*\nhid_bpf_destroy_device().\n\nhid_destroy_device\n` hid_bpf_destroy_device\n ` cleanup_srcu_struct(&hdev->bpf.srcu)\n` hid_remove_device\n ` ...\n ` led_classdev_unregister\n ` led_trigger_set(led_cdev, NULL)\n ` led_set_brightness(led_cdev, LED_OFF)\n ` ...\n ` input_inject_event\n ` input_event_dispose\n ` hidinput_input_event\n ` schedule_work(&hid->led_work) [hidinput_led_worker]\n\nThis is fine when condition B is not met, where hidinput_led_worker()\ncalls hid_ll_driver->request(). This is the case for most HID drivers,\nwhich implement it or use the generic one from usbhid. The driver itself\nor an underlying driver will then abort processing the request.\n\nOtherwise, hidinput_led_worker() tries hid_hw_output_report() and leads\nto the bug.\n\nhidinput_led_worker\n` hid_hw_output_report\n ` dispatch_hid_bpf_output_report\n ` srcu_read_lock(&hdev->bpf.srcu)\n ` srcu_read_unlock(&hdev->bpf.srcu, idx)\n\nThe bug has existed since the introduction [2] of\ndispatch_hid_bpf_output_report(). However, the same bug also exists in\ndispatch_hid_bpf_raw_requests(), and I've reproduced (no visible effect\nbecause of the lack of [1], but confirmed bpf.destroyed == 1) the bug\nagainst the commit (i.e., the Fixes:) introducing the function. This is\nbecause hidinput_led_worker() falls back to hid_hw_raw_request() when\nhid_ll_driver->output_report() is uninplemented (e.g., logitech-\ndjreceiver).\n\nhidinput_led_worker\n` hid_hw_output_report: -ENOSYS\n` hid_hw_raw_request\n ` dispatch_hid_bpf_raw_requests\n ` srcu_read_lock(&hdev->bpf.srcu)\n ` srcu_read_unlock(&hdev->bpf.srcu, idx)\n\nFix the issue by returning early in the two mentioned functions if\nhid_bpf has been marked as destroyed. Though\ndispatch_hid_bpf_device_event() handles input events, and there is no\nevidence that it may be called after the destruction, the same check, as\na safety net, is also added to it to maintain the consistency among all\ndispatch functions.\n\nThe impact of the bug on other architectures is unclear. Even if it acts\nas a hidden failure, this is still dangerous because it corrupts\nwhatever is on the address calculated by SRCU. Thus, CC'ing the stable\nlist.\n\n[1]: commit 9d7de2aa8b41 (\"x86/percpu/64: Use relative percpu offsets\")\n[2]: commit 9286675a2aed (\"HID: bpf: add HID-BPF hooks for\nhid_hw_output_report\")" } ], "metrics": [ { "cvssV3_1": { "version": "3.1", "vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "baseScore": 8.8, "baseSeverity": "HIGH" }, "scenarios": [ { "lang": "en", "value": "AV:A - The vulnerable teardown is driven by wireless HID transports whose ll_drivers lack ->request and implement ->output_report: a Logitech Unifying dj child device is destroyed purely by an over-the-air `REPORT_TYPE_NOTIF_DEVICE_UNPAIRED` notification on the unauthenticated 2.4 GHz link (hid-logitech-dj.c:1684), and Bluetooth HIDP (`hidp_hid_driver`, net/bluetooth/hidp/core.c:742) has the identical profile. No physical access to the machine and no local account are needed — only RF proximity.\nAC:L - The attacker controls both preconditions from its own peripheral: sending a CapsLock/NumLock keypress makes the host turn on an LED (the dj `kbd_descriptor` exposes a 5-LED output report), and an unpair/disconnect then destroys the HID device; the sequence is repeatable indefinitely and was reproduced deterministically by the reporter and an independent tester.\nPR:N - No credentials or privileges on the target system are required — the attacker acts as a HID peripheral, and the Unifying RF link authenticates neither keystrokes nor unpair notifications.\nUI:N - The attacker's own device generates both the LED state change and the disconnect/unpair event; no victim login, click, or plug/unplug action is involved.\nS:U - The freed SRCU per-CPU data and the corrupted per-CPU region are all kernel-internal state within a single security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - This is a use-after-free of the SRCU structure torn down by `cleanup_srcu_struct()`, and the resulting accesses hit the head of the running CPU's per-CPU area, which on x86-64 holds CPU control structures (`gdt_page`, `cpu_tss_rw`, `exception_stacks`); corrupting those is leverageable into arbitrary kernel memory disclosure.\nI:H - `__srcu_read_lock()`/`__srcu_read_unlock()` perform unconditional 8-byte increments through the freed/NULLed `ssp->sda`, silently modifying live kernel per-CPU data — the commit itself states it \"corrupts whatever is on the address calculated by SRCU\" and calls this dangerous, and GDT/TSS/exception-stack corruption is a control-flow-hijack primitive.\nA:H - On kernels with relative percpu offsets the access lands on a not-present page and oopses/panics the kernel, and on earlier trees the per-CPU corruption of CPU control structures crashes the machine; the attacker can retrigger it at will by repeating connect/LED/disconnect cycles." } ] } ], "affected": [ { "product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": [ "drivers/hid/bpf/hid_bpf_dispatch.c" ], "versions": [ { "version": "8bd0488b5ea58655ad6fdcbe0408ef49b16882b1", "lessThan": "f8544be7e8e55b0ef23e1ab90e23e8d4d4aad3d3", "status": "affected", "versionType": "git" }, { "version": "8bd0488b5ea58655ad6fdcbe0408ef49b16882b1", "lessThan": "e4b4fe25a4101d1ddb5884f40e149a3618983b66", "status": "affected", "versionType": "git" }, { "version": "8bd0488b5ea58655ad6fdcbe0408ef49b16882b1", "lessThan": "578e1b96fad7402ff7e9c7648c8f1ad0225147c8", "status": "affected", "versionType": "git" } ] }, { "product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": [ "drivers/hid/bpf/hid_bpf_dispatch.c" ], "versions": [ { "version": "6.11", "status": "affected" }, { "version": "0", "lessThan": "6.11", "status": "unaffected", "versionType": "semver" }, { "version": "6.12.30", "lessThanOrEqual": "6.12.*", "status": "unaffected", "versionType": "semver" }, { "version": "6.14.8", "lessThanOrEqual": "6.14.*", "status": "unaffected", "versionType": "semver" }, { "version": "6.15", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix" } ] } ], "cpeApplicability": [ { "nodes": [ { "operator": "OR", "negate": false, "cpeMatch": [ { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.11", "versionEndExcluding": "6.12.30" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.11", "versionEndExcluding": "6.14.8" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.11", "versionEndExcluding": "6.15" } ] } ] } ], "references": [ { "url": "https://git.kernel.org/stable/c/f8544be7e8e55b0ef23e1ab90e23e8d4d4aad3d3" }, { "url": "https://git.kernel.org/stable/c/e4b4fe25a4101d1ddb5884f40e149a3618983b66" }, { "url": "https://git.kernel.org/stable/c/578e1b96fad7402ff7e9c7648c8f1ad0225147c8" } ], "title": "HID: bpf: abort dispatch if device destroyed", "x_generator": { "engine": "bippy-1.2.0" } } } }