Answer in brief
CVE-2025-38134 records a Medium severity (CVSS 5.5) vulnerability in usb: acpi: Prevent null pointer dereference in usb_acpi_add_usb4_devlink(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f1bfb4a6fed64de1771b43a76631942279851744 <8fa544bff8466062e42949c93f3e528f4be5624b || >=f1bfb4a6fed64de1771b43a76631942279851744 <e3d530173b70514d4390a94f9f979acad689b70a || >=f1bfb4a6fed64de1771b43a76631942279851744 <73fb0ec9436ae87bcae067ce35d6cdd72bade86c | 8fa544bff8466062e42949c93f3e528f4be5624b, e3d530173b70514d4390a94f9f979acad689b70a, 73fb0ec9436ae87bcae067ce35d6cdd72bade86c |
| Linux/Linuxgeneric | 6.12 | Not reported |
Published upstream
Jul 3, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
In the Linux kernel, the following vulnerability has been resolved: usb: acpi: Prevent null pointer dereference in usb_acpi_add_usb4_devlink() As demonstrated by the fix for update_port_device_state, commit 12783c0b9e2c ("usb: core: Prevent null pointer dereference in update_port_device_state"), usb_hub_to_struct_hub() can return NULL in certain scenarios, such as during hub driver unbind or teardown race conditions, even if the underlying usb_device structure exists. Plus, all other places that call usb_hub_to_struct_hub() in the same file do check for NULL return values. If usb_hub_to_struct_hub() returns NULL, the subsequent access to hub->ports[udev->portnum - 1] will cause a null pointer dereference.
Quoted source text, attributed separately from HOL analysis.