Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-49080

mm/mempolicy: fix mpol_new leak in shared_policy_replace

Medium5.5EPSS 0.31%
Published
Updated
Reserved
Assigned by
Linux

Description

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

Scores

CVSS scores of CVE-2022-49080, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.31% · top 76% of all CVEs (6 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Weakness

Affected products

  • Linux · Linux

    • affected 42288fe366c4f1ce7522bc9f27d0bc2a81c55264 – < 8510c2346d9e47a72b7f018a36ef0c39483e53d6
    • affected 42288fe366c4f1ce7522bc9f27d0bc2a81c55264 – < 5e16dc5378abd749a836daa9ee4ab2c8d2668999
    • affected 42288fe366c4f1ce7522bc9f27d0bc2a81c55264 – < 39a32f3c06f6d68a530bf9612afa19f50f12e93d
    • affected 42288fe366c4f1ce7522bc9f27d0bc2a81c55264 – < 25f506273b6ae806fd46bfcb6fdaa5b9ec81a05b
    • affected 42288fe366c4f1ce7522bc9f27d0bc2a81c55264 – < f7e183b0a7136b6dc9c7b9b2a85a608a8feba894
    • affected 42288fe366c4f1ce7522bc9f27d0bc2a81c55264 – < 198932a14aeb19a15cf19e51e151d023bc4cd648
    • affected 42288fe366c4f1ce7522bc9f27d0bc2a81c55264 – < 6e00309ac716fa8225f0cbde2cd9c24f0e74ee21
    • affected 42288fe366c4f1ce7522bc9f27d0bc2a81c55264 – < fe39ac59dbbf893b73b24e3184161d0bd06d6651
    • affected 42288fe366c4f1ce7522bc9f27d0bc2a81c55264 – < 4ad099559b00ac01c3726e5c95dc3108ef47d03e
  • Linux · Linux

    • affected 3.8
    • unaffected < 3.8
    • unaffected 4.9.311 – ≤ 4.9.*
    • unaffected 4.14.276 – ≤ 4.14.*
    • unaffected 4.19.238 – ≤ 4.19.*
    • unaffected 5.4.189 – ≤ 5.4.*
    • unaffected 5.10.111 – ≤ 5.10.*
    • unaffected 5.15.34 – ≤ 5.15.*
    • unaffected 5.16.20 – ≤ 5.16.*
    • unaffected 5.17.3 – ≤ 5.17.*
    • unaffected 5.18 – ≤ *

References (9)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-49080 badge
[![CVE-2022-49080](https://trackcve.app/badge/CVE-2022-49080.svg)](https://trackcve.app/cve/CVE-2022-49080)

Record last updated .