Linux Kernel up to 5.17.2 mpol_new initialization

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.4$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Linux Kernel up to 5.17.2. This issue affects the function mpol_new. Performing a manipulation results in initialization. This vulnerability was named CVE-2022-49080. There is no available exploit. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Linux Kernel up to 5.17.2. This affects the function mpol_new. The manipulation with an unknown input leads to a initialization vulnerability. CWE is classifying the issue as CWE-665. The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used. The impact remains unknown. The summary by CVE is:

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

It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2022-49080 since 02/26/2025. The exploitability is told to be easy. Technical details of the vulnerability are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 232635 (SUSE SLES15 Security Update : kernel (SUSE-SU-2025:0833-2)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.9.311, 4.14.276, 4.19.238, 5.4.189, 5.10.111, 5.15.34, 5.16.20 or 5.17.3 eliminates this vulnerability. Applying the patch 8510c2346d9e47a72b7f018a36ef0c39483e53d6/5e16dc5378abd749a836daa9ee4ab2c8d2668999/39a32f3c06f6d68a530bf9612afa19f50f12e93d/25f506273b6ae806fd46bfcb6fdaa5b9ec81a05b/f7e183b0a7136b6dc9c7b9b2a85a608a8feba894/198932a14aeb19a15cf19e51e151d023bc4cd648/6e00309ac716fa8225f0cbde2cd9c24f0e74ee21/fe39ac59dbbf893b73b24e3184161d0bd06d6651/4ad099559b00ac01c3726e5c95dc3108ef47d03e is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (232635) and EUVD (EUVD-2022-55124). Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.4

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Initialization
CWE: CWE-665
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 232635
Nessus Name: SUSE SLES15 Security Update : kernel (SUSE-SU-2025:0833-2)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Kernel 4.9.311/4.14.276/4.19.238/5.4.189/5.10.111/5.15.34/5.16.20/5.17.3
Patch: 8510c2346d9e47a72b7f018a36ef0c39483e53d6/5e16dc5378abd749a836daa9ee4ab2c8d2668999/39a32f3c06f6d68a530bf9612afa19f50f12e93d/25f506273b6ae806fd46bfcb6fdaa5b9ec81a05b/f7e183b0a7136b6dc9c7b9b2a85a608a8feba894/198932a14aeb19a15cf19e51e151d023bc4cd648/6e00309ac716fa8225f0cbde2cd9c24f0e74ee21/fe39ac59dbbf893b73b24e3184161d0bd06d6651/4ad099559b00ac01c3726e5c95dc3108ef47d03e

Timelineinfo

02/26/2025 🔍
02/26/2025 +0 days 🔍
02/26/2025 +0 days 🔍
09/24/2025 +210 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2022-49080 (🔍)
GCVE (CVE): GCVE-0-2022-49080
GCVE (VulDB): GCVE-100-297543
EUVD: 🔍

Entryinfo

Created: 02/26/2025 12:11
Updated: 09/24/2025 03:04
Changes: 02/26/2025 12:11 (57), 03/12/2025 12:27 (2), 09/24/2025 01:49 (11), 09/24/2025 03:04 (1)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!