CVE-2025-40036
Description
In the Linux kernel, the following vulnerability has been resolved:
misc: fastrpc: fix possible map leak in fastrpc_put_args
copy_to_user() failure would cause an early return without cleaning up the fdlist, which has been updated by the DSP. This could lead to map leak. Fix this by redirecting to a cleanup path on failure, ensuring that all mapped buffers are properly released before returning.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A memory map leak in the Linux kernel's misc/fastrpc driver can occur when copy_to_user() fails after the DSP updates the fdlist, preventing proper cleanup.
Vulnerability
Overview
In the Linux kernel's FastRPC (fastrpc) driver, a vulnerability exists where a failure in copy_to_user() during the fastrpc_put_args function can cause a memory map leak. The issue arises because the fdlist, which has been updated by the DSP (Digital Signal Processor), is not cleaned up when the early return is taken on the failure path [1][2]. This omission leads to map leak, meaning that previously allocated buffers remain mapped and are not properly released.
Attack
Vector and Prerequisites
To exploit this vulnerability, an attacker needs to have the ability to invoke FastRPC operations and cause copy_to_user() to fail. This could be achieved via a race condition or by manipulating memory conditions such that the kernel's copy operation fails. The attacker does not require physical access but needs local access to the system and the ability to interact with the FastRPC subsystem, which is typically used for DSP communication on Qualcomm platforms.
Impact
If successfully exploited, an attacker could trigger a memory map leak, resulting in the exhaustion of system memory resources over time (denial of service). Repeated exploitation could lead to memory pressure, potentially causing system instability or crashes. No privilege escalation or data leakage is indicated in the provided description.
Mitigation
The fix has been applied in the Linux kernel stable tree, as referenced in commits [1] and [2]. Users should apply the kernel patch to correct the cleanup path, ensuring that on copy_to_user() failure, the fdlist is properly handled before returning. No KEV-listing or known exploitation in the wild has been mentioned.
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
53ad42dc6644578d33a041555c000f65f0ac9da1ba64176e0a085658264d0Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
5- git.kernel.org/stable/c/3ad42dc66445df6977cf4be0c06f1a655299ce6cnvd
- git.kernel.org/stable/c/78d33a041555db03903e8037fd053ed74fbd88cbnvd
- git.kernel.org/stable/c/a085658264d0c8d4f795d4631f77d7289a021de9nvd
- git.kernel.org/stable/c/c000f65f0ac93d9f9cc69a230d372f6ca93e4879nvd
- git.kernel.org/stable/c/da1ba64176e0138f2bfa96f9e43e8c3640d01e1envd
News mentions
0No linked articles in our index yet.