CVE-2025-38145

What it actually does

NULL pointer dereference in aspeed_lpc_enable_snoop() when devm_kasprintf() fails to allocate memory, leading to kernel crash on affected ASPEED hardware.

Why it matters to the business

Systems using affected Linux kernel versions on ASPEED-based platforms may experience unexpected crashes or instability during LPC snoop initialization, potentially disrupting operations on servers or embedded devices with high memory pressure.

How an attack unfolds

An attacker with local access or the ability to trigger memory exhaustion conditions on a system using the vulnerable ASPEED LPC driver can cause the unchecked NULL return from devm_kasprintf() to be dereferenced, resulting in a kernel panic; listed threat actors associated with similar Linux kernel privilege escalations highlight ongoing targeting of kernel memory issues.

How to fix it

Update to fixed kernel versions containing commit 2beee9cf833374550e673d428ad8b6ab37c175b3 or later stable releases; for nats-fips update to 0.2.3-r1 or newer.

How to confirm the fix worked

Verify presence of the NULL check after devm_kasprintf() in aspeed_lpc_enable_snoop() by inspecting kernel source or confirming updated package versions; test initialization under memory-constrained conditions.

Typical attack path

1. Identify target system running vulnerable Linux kernel with ASPEED LPC support enabled
2. Trigger or wait for memory allocation pressure during aspeed_lpc_enable_snoop() execution
3. Cause devm_kasprintf() to return NULL
4. Trigger NULL pointer dereference leading to kernel panic or denial of service

How to detect it

Review kernel logs for NULL pointer dereference panics referencing aspeed_lpc_enable_snoop or devm_kasprintf failures; correlate with memory pressure events and LPC driver initialization timestamps.

What your security team should do

• Prioritize patching Linux kernel on all ASPEED-equipped systems due to memory corruption family classification
• Monitor EPSS trend and kernel privilege escalation campaigns for increased exploitation likelihood
• Apply updates to fixed commit 2beee9cf833374550e673d428ad8b6ab37c175b3 or package equivalents immediately
• Restrict local access and monitor for memory exhaustion conditions on affected platforms