CVE-2022-49080

published 26 Feb 2025 · updated 11 May 2026

mm/mempolicy: fix mpol_new leak in shared_policy_replace

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 198932a14aeb19a15cf19e51e151d023bc4cd648, Kernel 25f506273b6ae806fd46bfcb6fdaa5b9ec81a05b, Kernel 39a32f3c06f6d68a530bf9612afa19f50f12e93d and 6 more.

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); }

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=3.8, >=42288fe366c4f1ce7522bc9f27d0bc2a81c55264 <198932a14aeb19a15cf19e51e151d023bc4cd648, >=42288fe366c4f1ce7522bc9f27d0bc2a81c55264 <25f506273b6ae806fd46bfcb6fdaa5b9ec81a05b, >=42288fe366c4f1ce7522bc9f27d0bc2a81c55264 <39a32f3c06f6d68a530bf9612afa19f50f12e93d, >=42288fe366c4f1ce7522bc9f27d0bc2a81c55264 <4ad099559b00ac01c3726e5c95dc3108ef47d03e, >=42288fe366c4f1ce7522bc9f27d0bc2a81c55264 <5e16dc5378abd749a836daa9ee4ab2c8d2668999, >=42288fe366c4f1ce7522bc9f27d0bc2a81c55264 <6e00309ac716fa8225f0cbde2cd9c24f0e74ee21, >=42288fe366c4f1ce7522bc9f27d0bc2a81c55264 <8510c2346d9e47a72b7f018a36ef0c39483e53d6, >=42288fe366c4f1ce7522bc9f27d0bc2a81c55264 <f7e183b0a7136b6dc9c7b9b2a85a608a8feba894, >=42288fe366c4f1ce7522bc9f27d0bc2a81c55264 <fe39ac59dbbf893b73b24e3184161d0bd06d6651198932a14aeb19a15cf19e51e151d023bc4cd648, 25f506273b6ae806fd46bfcb6fdaa5b9ec81a05b, 39a32f3c06f6d68a530bf9612afa19f50f12e93d, 4ad099559b00ac01c3726e5c95dc3108ef47d03e, 5e16dc5378abd749a836daa9ee4ab2c8d2668999, 6e00309ac716fa8225f0cbde2cd9c24f0e74ee21, 8510c2346d9e47a72b7f018a36ef0c39483e53d6, f7e183b0a7136b6dc9c7b9b2a85a608a8feba894, fe39ac59dbbf893b73b24e3184161d0bd06d6651

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2022-49080 severity on Zeptric[![CVE-2022-49080](https://zeptric.io/badge/cve/CVE-2022-49080.svg)](https://zeptric.io/cve/CVE-2022-49080)