[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091853-CVE-2022-50391-7caa@gregkh>
Date: Thu, 18 Sep 2025 15:34:05 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50391: mm/mempolicy: fix memory leak in set_mempolicy_home_node system call
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
mm/mempolicy: fix memory leak in set_mempolicy_home_node system call
When encountering any vma in the range with policy other than MPOL_BIND or
MPOL_PREFERRED_MANY, an error is returned without issuing a mpol_put on
the policy just allocated with mpol_dup().
This allows arbitrary users to leak kernel memory.
The Linux kernel CVE team has assigned CVE-2022-50391 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.17 with commit c6018b4b254971863bd0ad36bb5e7d0fa0f0ddb0 and fixed in 6.0.17 with commit 4ca0eb6b2f3add8c5daefb726ce57dc95d103d33
Issue introduced in 5.17 with commit c6018b4b254971863bd0ad36bb5e7d0fa0f0ddb0 and fixed in 6.1.3 with commit 0ce4cc6d269ddc448a825955b495f662f5d9e153
Issue introduced in 5.17 with commit c6018b4b254971863bd0ad36bb5e7d0fa0f0ddb0 and fixed in 6.2 with commit 38ce7c9bdfc228c14d7621ba36d3eebedd9d4f76
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2022-50391
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
mm/mempolicy.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/4ca0eb6b2f3add8c5daefb726ce57dc95d103d33
https://git.kernel.org/stable/c/0ce4cc6d269ddc448a825955b495f662f5d9e153
https://git.kernel.org/stable/c/38ce7c9bdfc228c14d7621ba36d3eebedd9d4f76
Powered by blists - more mailing lists