CVE-2026-99613 in Linux
Summary
by MITRE • 11/20/2026
In the Linux kernel, the following vulnerability has been resolved:
ALSA: cs46xx: Handle SCB creation failures before dereferencing
With CONFIG_PM_SLEEP enabled, cs46xx_dsp_create_scb() can return NULL if kmemdup() fails to allocate the SCB data saved for resume. cs46xx_dsp_scb_and_task_init() and _dsp_create_generic_scb() dereference the returned pointer without checking it, causing a NULL pointer dereference on allocation failure.
Check both return values before accessing the SCB descriptors. Return -ENOMEM when creating the null SCB fails and propagate NULL from _dsp_create_generic_scb().
Found by Linux Verification Center (linuxtesting.org) with SVACE static analysis tool.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability identified in the ALSA cs46xx audio driver within the Linux kernel represents a critical memory management flaw that can lead to system instability or denial of service conditions. This issue specifically manifests when the CONFIG_PM_SLEEP configuration option is enabled, which activates power-saving features for sleep states. Under these circumstances, the function cs46xx_dsp_create_scb() attempts to allocate memory using kmemdup to save Sound Control Block data required for resume operations. If this allocation fails due to system resource exhaustion or other constraints, the function returns a NULL pointer instead of a valid memory address. The core technical flaw lies in the subsequent handling of this return value by cs46xx_dsp_scb_and_task_init() and _dsp_create_generic_scb(), which proceed to dereference the returned pointer without performing any validity checks. This lack of defensive programming results in an immediate NULL pointer dereference, a classic error that typically causes kernel panics or crashes when the operating system attempts to access memory at address zero.
From a technical perspective, this vulnerability is classified under CWE-476, which denotes a NULL Pointer Dereference. The root cause is not a complex logic error but rather an omission in error handling routines where developers assumed successful allocation without verifying the outcome of dynamic memory requests. In high-load scenarios or systems with fragmented memory, kmemdup failures are more probable, increasing the attack surface for local denial-of-service attacks. An attacker who can induce memory pressure on the system might trigger this condition during device suspend or resume cycles, leading to a complete system crash. This aligns with MITRE ATT&CK technique T1499, Endpoint Denial of Service, where resource exhaustion is leveraged to disrupt normal operations. The vulnerability highlights the importance of rigorous validation of all dynamic memory allocations in kernel-space code, as failures there have far more severe consequences than in user space.
The operational impact of this flaw extends beyond simple application crashes; it affects system reliability and availability. Since the issue occurs during power state transitions involving sleep states, users may experience unexpected reboots or freezes when their systems attempt to enter or exit low-power modes while using cs46xx-based audio hardware. This undermines trust in the stability of Linux distributions that include this driver, particularly in server environments where uptime is critical and unplanned restarts are costly. Furthermore, such kernel-level crashes can potentially expose sensitive data if memory contents are dumped during a panic, although the primary impact remains availability disruption. The fix involves adding explicit checks for NULL return values before any dereferencing occurs. When allocation fails, the code now returns -ENOMEM to properly signal the error condition up the call stack and propagates this failure through _dsp_create_generic_scb(), ensuring that higher-level functions are aware of the resource shortage and can handle it gracefully rather than crashing.
Mitigation strategies for this vulnerability primarily involve applying the upstream kernel patch provided by Linux distribution maintainers, which introduces the necessary null checks and error propagation logic. Administrators should ensure their systems are updated to versions containing these fixes, particularly if they utilize power management features with cs46xx audio devices. For environments where immediate patching is not feasible, disabling CONFIG_PM_SLEEP for affected drivers can serve as a temporary workaround, though this may impact battery life on mobile devices or increase energy consumption in servers. Long-term remediation requires enforcing static analysis tools like SVACE during the development and integration phases of kernel modules to catch such omissions early. Developers must adopt a mindset where every pointer returned from memory allocation functions is treated as potentially invalid until explicitly verified, adhering to secure coding standards that prioritize robust error handling over assumed success paths.