CVE-2025-38454

What it actually does

Potential NULL pointer dereference in snd_card_ad1816a_pnp() when pdev is NULL because dev_warn() was used instead of pr_warn().

Why it matters to the business

Kernel instability or crashes on affected Alpine systems using intel-ucode packages can disrupt audio functionality and system availability across many downstream dependents.

How an attack unfolds

An attacker triggers snd_card_ad1816a_pnp() with a NULL pdev in specific PnP audio initialization paths, causing the kernel to dereference the NULL pointer.

How to fix it

Upgrade intel-ucode on Alpine v3.19 and v3.20 to fixed version 20250812-r0.

How to confirm the fix worked

Verify installed package version matches or exceeds 20250812-r0 and confirm absence of the vulnerable dev_warn call in the driver source.

Typical attack path

1. Identify system with ad1816a audio device or PnP registration
2. Force NULL pdev condition during snd_card_ad1816a_pnp execution
3. Trigger NULL dereference leading to kernel fault

How to detect it

Review kernel logs for ad1816a PnP initialization entries and NULL pointer warnings around the time of any crashes.

What your security team should do

• Apply the 20250812-r0 update to intel-ucode packages on all Alpine v3.19 and v3.20 systems
• Monitor kernel logs for ad1816a-related warnings during boot
• Prioritize patching given the memory corruption family classification