CVE-2025-38629: ALSA: usb: scarlett2: Fix missing NULL check
In the Linux kernel, the following vulnerability has been resolved:
ALSA: usb: scarlett2: Fix missing NULL check
scarlett2inputselectctlinfo() sets up the string arrays allocated via kasprintf(), but it misses NULL checks, which may lead to NULL dereference Oops. Let's add the proper NULL check.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.15.10 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.16.1 - Upgrade
Upgrade
ubuntu/linux-aws-6.14to a version that resolves this vulnerability.Fixed in 6.14.0-1017.17~24.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-6.14to a version that resolves this vulnerability.Fixed in 6.14.0-1017.17~24.04.1 - Upgrade
Upgrade
ubuntu/linux-gcp-6.14to a version that resolves this vulnerability.Fixed in 6.14.0-1020.21~24.04.1 - Upgrade
Upgrade
ubuntu/linux-oem-6.14to a version that resolves this vulnerability.Fixed in 6.14.0-1016.16 - Upgrade
Upgrade
ubuntu/linux-oracle-6.14to a version that resolves this vulnerability.Fixed in 6.14.0-1017.17~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-6.14to a version that resolves this vulnerability.Fixed in 6.14.0-36.36.1~24.04.1 - Upgrade
Upgrade
ubuntu/linux-realtime-6.14to a version that resolves this vulnerability.Fixed in 6.14.0-1016.16~24.04.1
Event History
Frequently Asked Questions
What is the severity of CVE-2025-38629?
CVE-2025-38629 has not been assigned a severity rating yet.
How do I fix CVE-2025-38629?
To fix CVE-2025-38629, ensure your Linux kernel is updated to the latest version where the NULL check has been implemented.
What systems are affected by CVE-2025-38629?
CVE-2025-38629 affects the Linux kernel, particularly versions that include the ALSA subsystem.
What risks are associated with CVE-2025-38629?
CVE-2025-38629 could lead to a NULL pointer dereference, resulting in a potential system crash.
Is there a workaround for CVE-2025-38629?
There are no known workarounds for CVE-2025-38629; updating the kernel is recommended for mitigation.