lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024110934-CVE-2024-50244-54e5@gregkh>
Date: Sat,  9 Nov 2024 11:15:52 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-50244: fs/ntfs3: Additional check in ni_clear()

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

fs/ntfs3: Additional check in ni_clear()

Checking of NTFS_FLAGS_LOG_REPLAYING added to prevent access to
uninitialized bitmap during replay process.

The Linux kernel CVE team has assigned CVE-2024-50244 to this issue.


Affected and fixed versions
===========================

	Fixed in 5.15.171 with commit 60fb94ef46c2
	Fixed in 6.1.116 with commit 14a23e15a5e8
	Fixed in 6.6.60 with commit 7a4ace681dbb
	Fixed in 6.11.7 with commit 80824967ec71
	Fixed in 6.12-rc3 with commit d178944db36b

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-2024-50244
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/frecord.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/60fb94ef46c2359dd06cbe30bfc2499f639433df
	https://git.kernel.org/stable/c/14a23e15a5e8331bb0cf21288723fa530a45b2a4
	https://git.kernel.org/stable/c/7a4ace681dbb652aeb40e1b88f9134b880fdeeb5
	https://git.kernel.org/stable/c/80824967ec714dda02cd79091aa186bbc16c5cf3
	https://git.kernel.org/stable/c/d178944db36b3369b78a08ba520de109b89bf2a9

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ