misc: fastrpc: Don't remove map on creater_process and device_release
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
aaf5aa44934ad069cac805923c49f6968b9a0d49| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
misc: fastrpc: Don't remove map on creater_process and device_release
Do not remove the map from the list on error path in fastrpc_init_create_process, instead call fastrpc_map_put, to avoid use-after-free. Do not remove it on fastrpc_device_release either, call fastrpc_map_put instead.
The fastrpc_free_map is the only proper place to remove the map. This is called only after the reference count is 0.
From the CVE record · Linux
The Linux kernel's fastrpc code can use a map after it has been freed when process creation takes an error path or a device is released. The input does not specify how an attacker could trigger this, or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with fastrpc should check their versions; affected versions are not specified.