[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025121624-CVE-2025-68253-7e3c@gregkh>
Date: Tue, 16 Dec 2025 15:32:29 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-68253: mm: don't spin in add_stack_record when gfp flags don't allow
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
mm: don't spin in add_stack_record when gfp flags don't allow
syzbot was able to find the following path:
add_stack_record_to_list mm/page_owner.c:182 [inline]
inc_stack_record_count mm/page_owner.c:214 [inline]
__set_page_owner+0x2c3/0x4a0 mm/page_owner.c:333
set_page_owner include/linux/page_owner.h:32 [inline]
post_alloc_hook+0x240/0x2a0 mm/page_alloc.c:1851
prep_new_page mm/page_alloc.c:1859 [inline]
get_page_from_freelist+0x21e4/0x22c0 mm/page_alloc.c:3858
alloc_pages_nolock_noprof+0x94/0x120 mm/page_alloc.c:7554
Don't spin in add_stack_record_to_list() when it is called
from *_nolock() context.
The Linux kernel CVE team has assigned CVE-2025-68253 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.15 with commit 97769a53f117e2f33864c587d85992ee35194ecf and fixed in 6.17.6 with commit 504174133453e3af73e626e328603d7eb5986f34
Issue introduced in 6.15 with commit 97769a53f117e2f33864c587d85992ee35194ecf and fixed in 6.18 with commit c83aab85e18103a6dc066b4939e2c92a02bb1b05
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-2025-68253
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/page_owner.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/504174133453e3af73e626e328603d7eb5986f34
https://git.kernel.org/stable/c/c83aab85e18103a6dc066b4939e2c92a02bb1b05
Powered by blists - more mailing lists