CVE-2025-40059
Description
In the Linux kernel, the following vulnerability has been resolved:
coresight: Fix incorrect handling for return value of devm_kzalloc
The return value of devm_kzalloc could be an null pointer, use "!desc.pdata" to fix incorrect handling return value of devm_kzalloc.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A null-pointer dereference in Linux kernel's Coresight driver, caused by incorrect handling of devm_kzalloc return values, leads to system instability under low-memory conditions.
Vulnerability
Analysis of CVE-2025-40059
The vulnerability exists in the Linux kernel's Coresight subsystem, specifically in the handling of memory allocation via devm_kzalloc. The fix corrects the check of the return value, replacing an incorrect condition with !desc.pdata to properly detect a null pointer returned by devm_kzalloc [1]. This is a classic null-pointer dereference bug, where a failed memory allocation (out-of-memory condition) would result in the driver proceeding with an uninitialized pointer, potentially leading to a crash or unpredictable behavior.
Exploitation requires the ability to trigger memory pressure in the kernel such that devm_kzalloc fails. This is a local condition; an attacker with low privileges could potentially cause memory exhaustion, e.g., by triggering numerous memory allocations or exhausting the kmem cache. The attack surface is limited to systems where the Coresight driver is loaded, typically hardware that implements the ARM CoreSight debug and trace architecture [1]. No special permissions beyond local access and the ability to influence system memory usage are required.
The impact of a successful exploitation is a kernel null-pointer dereference, leading to a system crash (kernel panic) or denial of service. This could be leveraged to cause significant disruption, especially in embedded or real-time systems that use CoreSight for debugging. The vulnerability is fixed in the Linux kernel stable repository [1]; users should update to a kernel version containing the commit referenced. There is no known workaround other than ensuring adequate memory or using memory cgroups to prevent local memory exhaustion.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
370714eb7243e8c4e7e646d5d9688b66d0a5eVulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
3News mentions
0No linked articles in our index yet.