linux-cve-announce - CVE-2024-50243: fs/ntfs3: Fix general protection fault in run_is_mapped

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-50243-fdd6@gregkh>
Date: Sat,  9 Nov 2024 11:15:51 +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-50243: fs/ntfs3: Fix general protection fault in run_is_mapped_full

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

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

fs/ntfs3: Fix general protection fault in run_is_mapped_full

Fixed deleating of a non-resident attribute in ntfs_create_inode()
rollback.

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


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

	Fixed in 6.6.60 with commit 68b39c0765de
	Fixed in 6.11.7 with commit 8e87c9aa8cf9
	Fixed in 6.12-rc3 with commit a33fb016e49e

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-50243
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/68b39c0765de7c97b34889c1f5e81c2a223fdacc
	https://git.kernel.org/stable/c/8e87c9aa8cf92cfceaff0aab244318bbb8b35137
	https://git.kernel.org/stable/c/a33fb016e49e37aafab18dc3c8314d6399cb4727