[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025022611-CVE-2022-49166-7308@gregkh>
Date: Wed, 26 Feb 2025 02:56:11 +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-49166: ntfs: add sanity check on allocation size
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ntfs: add sanity check on allocation size
ntfs_read_inode_mount invokes ntfs_malloc_nofs with zero allocation
size. It triggers one BUG in the __ntfs_malloc function.
Fix this by adding sanity check on ni->attr_list_size.
The Linux kernel CVE team has assigned CVE-2022-49166 to this issue.
Affected and fixed versions
===========================
Fixed in 4.9.311 with commit bd8d7daa0e53b184a2f3c6e0d47330780d0a0650
Fixed in 4.14.276 with commit 21d490232f323ed4053eb9924615e6fea291f154
Fixed in 4.19.238 with commit 07793d2e55563124108762f4e5f811db92ffe02f
Fixed in 5.4.189 with commit fe41ad8be036a3de3e4bdde709551aeb4de2fe7d
Fixed in 5.10.110 with commit b230f2d9441a34c7f483d39ab78519bcf73cc2e0
Fixed in 5.15.33 with commit 24ab2d4ef52c2dbb62a60844b87fc8872383407a
Fixed in 5.16.19 with commit 115fae2c1566eacc5ad2055f72521354612e72c3
Fixed in 5.17.2 with commit c641087d381a08363e5f14179bc6b0a23eca7c47
Fixed in 5.18 with commit 714fbf2647b1a33d914edd695d4da92029c7e7c0
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-49166
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/ntfs/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/bd8d7daa0e53b184a2f3c6e0d47330780d0a0650
https://git.kernel.org/stable/c/21d490232f323ed4053eb9924615e6fea291f154
https://git.kernel.org/stable/c/07793d2e55563124108762f4e5f811db92ffe02f
https://git.kernel.org/stable/c/fe41ad8be036a3de3e4bdde709551aeb4de2fe7d
https://git.kernel.org/stable/c/b230f2d9441a34c7f483d39ab78519bcf73cc2e0
https://git.kernel.org/stable/c/24ab2d4ef52c2dbb62a60844b87fc8872383407a
https://git.kernel.org/stable/c/115fae2c1566eacc5ad2055f72521354612e72c3
https://git.kernel.org/stable/c/c641087d381a08363e5f14179bc6b0a23eca7c47
https://git.kernel.org/stable/c/714fbf2647b1a33d914edd695d4da92029c7e7c0
Powered by blists - more mailing lists