linux-cve-announce - CVE-2024-50245: fs/ntfs3: Fix possible deadlock in mi

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-50245-87aa@gregkh>
Date: Sat,  9 Nov 2024 11:15:53 +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-50245: fs/ntfs3: Fix possible deadlock in mi_read

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

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

fs/ntfs3: Fix possible deadlock in mi_read

Mutex lock with another subclass used in ni_lock_dir().

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


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

	Fixed in 5.15.171 with commit 47e8a17491e3
	Fixed in 6.1.116 with commit c8e7d3b72ee5
	Fixed in 6.6.60 with commit 34e3220efd66
	Fixed in 6.11.7 with commit f1bc362fe978
	Fixed in 6.12-rc3 with commit 03b097099eef

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-50245
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/namei.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/47e8a17491e37df53743bc2e72309f8f0d6224af
	https://git.kernel.org/stable/c/c8e7d3b72ee57e43d58ba560fe7970dd840a4061
	https://git.kernel.org/stable/c/34e3220efd666d49965a26840d39f27601ce70f4
	https://git.kernel.org/stable/c/f1bc362fe978952a9304bd0286788b0ae7724f14
	https://git.kernel.org/stable/c/03b097099eef255fbf85ea6a786ae3c91b11f041