CVE-2022-49080
Last modified
CVE-2022-49080 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.26% chance of exploitation in the next 30 days.
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); }
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 3.8.1, < 4.9.311 | — |
| Linux | Linux Kernel | >= 4.10, < 4.14.276 | — |
| Linux | Linux Kernel | >= 4.15, < 4.19.238 | — |
| Linux | Linux Kernel | >= 4.20, < 5.4.189 | — |
| Linux | Linux Kernel | >= 5.5, < 5.10.111 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.34 | — |
| Linux | Linux Kernel | >= 5.16, < 5.16.20 | — |
| Linux | Linux Kernel | >= 5.17, < 5.17.3 | — |
| Linux | Linux Kernel | 3.8 | — |
| Linux | Linux Kernel | 5.18 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2022-49080?
How severe is CVE-2022-49080?
How do I fix CVE-2022-49080?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-49075In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49076In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-49077In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49078In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-49079In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-4908Inappropriate implementation in iFrame Sandbox in Google Chr…4.3
- CVE-2022-49081In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49082In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-49083In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49084In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49085In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-49086In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2022-49080?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST