Vulnerability in linux-hwe-edge
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as UBUNTU-CVE-2025-38016 has been found in linux-hwe-edge.
Risk of unauthorized operations or information disclosure.
What to do: upgrade linux-hwe-edge to 6.14.0-1011.11~24.04.1 or later.
If unsure, ask your IT team or search "linux-hwe-edge UBUNTU-CVE-2025-38016" on the vendor's site.
UBUNTU-CVE-2025-38016 (linux-hwe-edge)
Attack vector: local / no user interaction
Patched: 6.14.0-1011.11~24.04.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in linux-hwe-edge.
Check the vendor advisory for the affected versions of linux-hwe-edge.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 6.14.0-1011.11~24.04.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'linux-hwe-edge' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
grep -r 'linux-hwe-edge' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
linux-hwe-edgeを grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply patchpatch
Upgrade linux-hwe-edge to 6.14.0-1011.11~24.04.1ステージング環境で 6.14.0-1011.11~24.04.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| Ubuntu:16.04:LTS | linux-hwe-edge |
All versions |
— |
| Ubuntu:18.04:LTS | linux-aws-5.0 |
All versions |
— |
| Ubuntu:18.04:LTS | linux-aws-5.3 |
All versions |
— |
| Ubuntu:18.04:LTS | linux-azure |
All versions |
— |
| Ubuntu:18.04:LTS | linux-azure-5.3 |
All versions |
— |
| Ubuntu:18.04:LTS | linux-azure-edge |
All versions |
— |
| Ubuntu:18.04:LTS | linux-gcp |
All versions |
— |
| Ubuntu:18.04:LTS | linux-gcp-5.3 |
All versions |
— |
| Ubuntu:18.04:LTS | linux-gke-4.15 |
All versions |
— |
| Ubuntu:18.04:LTS | linux-gke-5.4 |
All versions |
— |
| Ubuntu:18.04:LTS | linux-gkeop-5.4 |
All versions |
— |
| Ubuntu:18.04:LTS | linux-hwe |
All versions |
— |
| Ubuntu:18.04:LTS | linux-hwe-edge |
All versions |
— |
| Ubuntu:18.04:LTS | linux-oem |
All versions |
— |
| Ubuntu:18.04:LTS | linux-oracle-5.0 |
All versions |
— |
| Ubuntu:18.04:LTS | linux-oracle-5.3 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-aws-5.11 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-aws-5.13 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-aws-5.8 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-azure-5.11 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-azure-5.13 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-azure-5.8 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-azure-fde |
All versions |
— |
| Ubuntu:20.04:LTS | linux-gcp-5.11 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-gcp-5.13 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-gcp-5.8 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-gke |
All versions |
— |
| Ubuntu:20.04:LTS | linux-gke-5.15 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-gkeop |
All versions |
— |
| Ubuntu:20.04:LTS | linux-gkeop-5.15 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-hwe-5.11 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-hwe-5.13 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-hwe-5.8 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-intel-5.13 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-oem-5.10 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-oem-5.13 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-oem-5.14 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-oem-5.6 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-oracle-5.11 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-oracle-5.13 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-oracle-5.8 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-raspi2 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-riscv |
All versions |
— |
| Ubuntu:20.04:LTS | linux-riscv-5.11 |
All versions |
— |
| Ubuntu:20.04:LTS | linux-riscv-5.8 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-aws-5.19 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-aws-6.2 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-aws-6.5 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-azure-5.19 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-azure-6.2 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-azure-6.5 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-gcp-5.19 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-gcp-6.2 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-gcp-6.5 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-hwe-5.19 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-hwe-6.2 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-hwe-6.5 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime |
All versions |
— |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-oem-5.17 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-oem-6.0 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-oem-6.1 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-oem-6.5 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-oracle-6.5 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-realtime |
All versions |
— |
| Ubuntu:22.04:LTS | linux-riscv |
All versions |
— |
| Ubuntu:22.04:LTS | linux-riscv-5.19 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-riscv-6.5 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-starfive-5.19 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-starfive-6.2 |
All versions |
— |
| Ubuntu:22.04:LTS | linux-starfive-6.5 |
All versions |
— |
| Ubuntu:24.04:LTS | linux-aws-6.14 |
< 6.14.0-1011.11~24.04.1 |
6.14.0-1011.11~24.04.1 |
| Ubuntu:24.04:LTS | linux-azure-6.11 |
All versions |
— |
| Ubuntu:24.04:LTS | linux-azure-fde-6.17 |
All versions |
— |
| Ubuntu:24.04:LTS | linux-gcp-6.11 |
All versions |
— |
| Ubuntu:24.04:LTS | linux-gcp-6.14 |
< 6.14.0-1014.15~24.04.1 |
6.14.0-1014.15~24.04.1 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 |
All versions |
— |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 |
All versions |
— |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 |
< 6.11.0-1013.13 |
6.11.0-1013.13 |
| Ubuntu:24.04:LTS | linux-oem-6.11 |
All versions |
— |
| Ubuntu:24.04:LTS | linux-oem-6.14 |
< 6.14.0-1010.10 |
6.14.0-1010.10 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 |
< 6.14.0-1011.11~24.04.1 |
6.14.0-1011.11~24.04.1 |
| Ubuntu:24.04:LTS | linux-raspi-realtime |
All versions |
— |
| Ubuntu:24.04:LTS | linux-realtime |
All versions |
— |
| Ubuntu:24.04:LTS | linux-riscv |
All versions |
— |
| Ubuntu:24.04:LTS | linux-riscv-6.14 |
< 6.14.0-28.28.1~24.04.1 |
6.14.0-28.28.1~24.04.1 |
| Ubuntu:Pro:Realtime:24.04:LTS | linux-realtime-6.14 |
< 6.14.0-1010.10~24.04.1 |
6.14.0-1010.10~24.04.1 |
| Ubuntu:25.10 | linux-azure-fde |
All versions |
— |
| Ubuntu:26.04 | linux-nvidia |
All versions |
— |
| Ubuntu:Nvidia-BlueField:24.04:LTS | linux-bluefield |
All versions |
— |
Original description The description as published by the source.
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…
Source: OSV.dev (Open Source Vulnerabilities) OSV
References
- advisory ubuntu.com
- advisory ubuntu.com
- advisory ubuntu.com
- report ubuntu.com
- report cve.org
- report git.kernel.org
- report git.kernel.org
- report git.kernel.org
- report git.kernel.org