Kernel crash via unchecked device-name allocation
Published May 9, 2025 · Updated May 11, 2026
NULL pointer dereference in the Aspeed virtual-hub USB gadget driver allows local users to crash affected Linux kernels. In ast_vhub_init_dev(), devm_kasprintf() can return NULL for d->name, but the function dereferences that value without checking allocation success. Reaching the fault requires the affected Aspeed virtual-hub driver and an allocation failure during device initialization; the bounded consequence is a kernel crash that interrupts service.
Summary
What happened
NULL pointer dereference in the Aspeed virtual-hub USB gadget driver allows local users to crash affected Linux kernels. In ast_vhub_init_dev(), devm_kasprintf() can return NULL for d->name, but the function dereferences that value without checking allocation success. Reaching the fault requires the affected Aspeed virtual-hub driver and an allocation failure during device initialization; the bounded consequence is a kernel crash that interrupts service.
The record
- CVE
- CVE-2025-37881
- Published
- May 9, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 9, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.18
- Affected versionversion=7ecca2a4080cb6b1fa174adc588fce9e9014c43c <052fb65335befeae8500e88d69ea022266baaf6d
- Affected versionversion=7ecca2a4080cb6b1fa174adc588fce9e9014c43c <36d68151712e525450f0fbb3045e7110f0d9b610
- Affected versionversion=7ecca2a4080cb6b1fa174adc588fce9e9014c43c <61006ca381b4d65d2b8ca695ea8da1ce18d6dee3
- Affected versionversion=7ecca2a4080cb6b1fa174adc588fce9e9014c43c <8c75f3e6a433d92084ad4e78b029ae680865420f
- Affected versionversion=7ecca2a4080cb6b1fa174adc588fce9e9014c43c <a777ccfb9ba8d43f745e41b69ba39d4a506a081e
- Affected versionversion=7ecca2a4080cb6b1fa174adc588fce9e9014c43c <c8d4faf452a627f9b09c3a5c366133a19e5b7a28
- Affected versionversion=7ecca2a4080cb6b1fa174adc588fce9e9014c43c <cfa7984f69359761b07a7831c1258c0fde1e0389
- Affected versionversion=7ecca2a4080cb6b1fa174adc588fce9e9014c43c <d26a6093d52904cacdbb75424c323c19b443a890
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo