CVE-2025-68253: mm: don't spin in add_stack_record when gfp flags don't allow
In the Linux kernel, the following vulnerability has been resolved:
mm: don't spin in addstackrecord when gfp flags don't allow
syzbot was able to find the following path: addstackrecordtolist mm/pageowner.c:182 [inline] incstackrecordcount mm/pageowner.c:214 [inline] setpageowner+0x2c3/0x4a0 mm/pageowner.c:333 setpageowner include/linux/pageowner.h:32 [inline] postallochook+0x240/0x2a0 mm/pagealloc.c:1851 prepnewpage mm/pagealloc.c:1859 [inline] getpagefromfreelist+0x21e4/0x22c0 mm/pagealloc.c:3858 allocpagesnolocknoprof+0x94/0x120 mm/pagealloc.c:7554
Don't spin in addstackrecordtolist() when it is called from nolock() context.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-68253?
CVE-2025-68253 is classified as a medium severity vulnerability in the Linux kernel.
How do I fix CVE-2025-68253?
To fix CVE-2025-68253, update your Linux kernel to the latest version that includes the patch for this vulnerability.
What systems are affected by CVE-2025-68253?
CVE-2025-68253 affects various versions of the Linux kernel across different distributions.
What impact does CVE-2025-68253 have on system performance?
CVE-2025-68253 can lead to performance degradation due to spinning in the add_stack_record function under certain memory allocation conditions.
Is CVE-2025-68253 remotely exploitable?
CVE-2025-68253 is not considered remotely exploitable but can affect local processes in Linux environments.