[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025011143-CVE-2024-51729-799d@gregkh>
Date: Sat, 11 Jan 2025 13:35:48 +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-51729: mm: use aligned address in copy_user_gigantic_page()
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
mm: use aligned address in copy_user_gigantic_page()
In current kernel, hugetlb_wp() calls copy_user_large_folio() with the
fault address. Where the fault address may be not aligned with the huge
page size. Then, copy_user_large_folio() may call
copy_user_gigantic_page() with the address, while
copy_user_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
copy_user_gigantic_page().
The Linux kernel CVE team has assigned CVE-2024-51729 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.11 with commit 530dd9926dc16220d2fae0997f45cda94f5f0864 and fixed in 6.12.7 with commit cb12d61361ce769672c7c7bd32107252598cdd8b
Issue introduced in 6.11 with commit 530dd9926dc16220d2fae0997f45cda94f5f0864 and fixed in 6.13-rc4 with commit f5d09de9f1bf9674c6418ff10d0a40cfe29268e1
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-51729
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:
mm/hugetlb.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/cb12d61361ce769672c7c7bd32107252598cdd8b
https://git.kernel.org/stable/c/f5d09de9f1bf9674c6418ff10d0a40cfe29268e1
Powered by blists - more mailing lists