linux-cve-announce - CVE-2024-52319: mm: use aligned address in clear_gigantic

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025011143-CVE-2024-52319-61ca@gregkh>
Date: Sat, 11 Jan 2025 13:35:49 +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-52319: mm: use aligned address in clear_gigantic_page()

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

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

mm: use aligned address in clear_gigantic_page()

In current kernel, hugetlb_no_page() calls folio_zero_user() with the
fault address.  Where the fault address may be not aligned with the huge
page size.  Then, folio_zero_user() may call clear_gigantic_page() with
the address, while clear_gigantic_page() requires the address to be huge
page size aligned.  So, this may cause memory corruption or information
leak, addtional, use more obvious naming 'addr_hint' instead of 'addr' for
clear_gigantic_page().

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


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

	Issue introduced in 6.11 with commit 78fefd04c123493bbf28434768fa577b2153c79b and fixed in 6.12.7 with commit b79b6fe0737f233f0be1465052b7f0e75f324735
	Issue introduced in 6.11 with commit 78fefd04c123493bbf28434768fa577b2153c79b and fixed in 6.13-rc4 with commit 8aca2bc96c833ba695ede7a45ad7784c836a262e

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-52319
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/hugetlbfs/inode.c
	mm/memory.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/b79b6fe0737f233f0be1465052b7f0e75f324735
	https://git.kernel.org/stable/c/8aca2bc96c833ba695ede7a45ad7784c836a262e