linux-cve-announce - CVE-2024-50248: ntfs3: Add bounds checking to mi_enum

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: <2024110936-CVE-2024-50248-619f@gregkh>
Date: Sat,  9 Nov 2024 11:15:56 +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-50248: ntfs3: Add bounds checking to mi_enum_attr()

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

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

ntfs3: Add bounds checking to mi_enum_attr()

Added bounds checking to make sure that every attr don't stray beyond
valid memory region.

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


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

	Fixed in 6.6.60 with commit 22cdf3be7d34
	Fixed in 6.11.7 with commit 809f9b419c75
	Fixed in 6.12-rc3 with commit 556bdf27c2dd

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-50248
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/record.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/22cdf3be7d34f61a91b9e2966fec3a29f3871398
	https://git.kernel.org/stable/c/809f9b419c75f8042c58434d2bfe849140643e9d
	https://git.kernel.org/stable/c/556bdf27c2dd5c74a9caacbe524b943a6cd42d99