misc: fastrpc: possible double-free of cctx->remote_heap
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
misc: fastrpc: possible double-free of cctx->remote_heap
fastrpc_init_create_static_process() may free cctx->remote_heap on the err_map path but does not clear the pointer. Later, fastrpc_rpmsg_remove() frees cctx->remote_heap again if it is non-NULL, which can lead to a double-free if the INIT_CREATE_STATIC ioctl hits the error path and the rpmsg device is subsequently removed/unbound. Clear cctx->remote_heap after freeing it in the error path to prevent the later cleanup from freeing it again.
This issue was found by an in-house analysis workflow that extracts AST-based information and runs static checks, with LLM assistance for triage, and was confirmed by manual code review. No hardware testing was performed.
From the CVE record · Linux
The Linux kernel’s fastrpc code can free cctx->remote_heap twice. This can occur when an INIT_CREATE_STATIC ioctl takes an error path and the rpmsg device is later removed or unbound. The input does not establish attacker access requirements or whether user interaction is needed.
Engineers running Linux kernels with fastrpc should check their kernel version against the vendor advisory; affected versions were not provided.