misc: fastrpc: take fl->lock when moving mmaps on interrupted invoke
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: take fl->lock when moving mmaps on interrupted invoke
When an invoke is interrupted by a signal, wait_for_completion_interruptible() returns -ERESTARTSYS and fastrpc_internal_invoke() moves every buffer from fl->mmaps onto cctx->invoke_interrupted_mmaps. This list_del()/list_add_tail() walk runs without holding fl->lock, the lock that serialises fl->mmaps in fastrpc_req_mmap() and fastrpc_req_munmap() everywhere else.
Take fl->lock around the move, matching every other fl->mmaps accessor.
From the CVE record · Linux
The Linux kernel fastrpc driver moves memory-mapping entries without holding the lock that protects their list. The race can occur when a signal interrupts an invoke while memory mappings are being changed; the provided information does not specify a resulting exploit or impact.
Engineers running Linux kernels with the fastrpc driver should check whether their kernel includes the fix; affected versions were not provided.