[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025022616-CVE-2022-49550-29a9@gregkh>
Date: Wed, 26 Feb 2025 03:13:44 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2022-49550: fs/ntfs3: provide block_invalidate_folio to fix memory leak
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
fs/ntfs3: provide block_invalidate_folio to fix memory leak
The ntfs3 filesystem lacks the 'invalidate_folio' method and it causes
memory leak. If you write to the filesystem and then unmount it, the
cached written data are not freed and they are permanently leaked.
The Linux kernel CVE team has assigned CVE-2022-49550 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.18 with commit 7ba13abbd31ee9265e88d7dc029c0f786e665192 and fixed in 5.18.3 with commit 0753245a72ec99824677586499ee2e0919164b3f
Issue introduced in 5.18 with commit 7ba13abbd31ee9265e88d7dc029c0f786e665192 and fixed in 5.19 with commit 724bbe49c5e427cb077357d72d240a649f2e4054
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-49550
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:
fs/ntfs3/inode.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/0753245a72ec99824677586499ee2e0919164b3f
https://git.kernel.org/stable/c/724bbe49c5e427cb077357d72d240a649f2e4054
Powered by blists - more mailing lists