mm/mempolicy: fix mpol_new leak in shared_policy_replace
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 42288fe366c4f1ce7522bc9f27d0bc2a81c55264 · < 198932a14aeb19a15cf19e51e151d023bc4cd648| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mm/mempolicy: fix mpol_new leak in shared_policy_replace
If mpol_new is allocated but not used in restart loop, mpol_new will be freed via mpol_put before returning to the caller. But refcnt is not initialized yet, so mpol_put could not do the right things and might leak the unused mpol_new. This would happen if mempolicy was updated on the shared shmem file while the sp->lock has been dropped during the memory allocation.
This issue could be triggered easily with the below code snippet if there are many processes doing the below work at the same time:
shmid = shmget((key_t)5566, 1024 * PAGE_SIZE, 0666|IPC_CREAT); shm = shmat(shmid, 0, 0); loop many times { mbind(shm, 1024 * PAGE_SIZE, MPOL_LOCAL, mask, maxnode, 0); mbind(shm + 128 * PAGE_SIZE, 128 * PAGE_SIZE, MPOL_DEFAULT, mask, maxnode, 0); }
From the CVE record · Linux
The Linux kernel can leak an unused mempolicy allocation in shared_policy_replace when a shared memory policy changes during allocation. A local attacker could trigger the leak by repeatedly changing the policy on shared memory while other processes do the same. No separate user interaction is described.
Engineers running the Linux kernel should check their kernel versions against the vendor advisory; affected versions are not specified in the input.