[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025121622-CVE-2025-68321-72b0@gregkh>
Date: Tue, 16 Dec 2025 16:44:23 +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-68321: page_pool: always add GFP_NOWARN for ATOMIC allocations
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
page_pool: always add GFP_NOWARN for ATOMIC allocations
Driver authors often forget to add GFP_NOWARN for page allocation
from the datapath. This is annoying to users as OOMs are a fact
of life, and we pretty much expect network Rx to hit page allocation
failures during OOM. Make page pool add GFP_NOWARN for ATOMIC allocations
by default.
The Linux kernel CVE team has assigned CVE-2025-68321 to this issue.
Affected and fixed versions
===========================
Fixed in 5.15.197 with commit 0ec2cd5c58793d0c622797cd5fbe26634b357210
Fixed in 6.1.159 with commit 9835a0fd59a1df5ec0740fdab6d50db68e0f10de
Fixed in 6.6.117 with commit 7613c06ffa89c1e2266fb532e23ef7dfdf269d73
Fixed in 6.12.58 with commit 3671a0775952026228ae44e096eb144bca75f8dc
Fixed in 6.17.8 with commit ab48dc0e23eb714b3f233f8e8f6deed7df2051f5
Fixed in 6.18 with commit f3b52167a0cb23b27414452fbc1278da2ee884fc
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-68321
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:
net/core/page_pool.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/0ec2cd5c58793d0c622797cd5fbe26634b357210
https://git.kernel.org/stable/c/9835a0fd59a1df5ec0740fdab6d50db68e0f10de
https://git.kernel.org/stable/c/7613c06ffa89c1e2266fb532e23ef7dfdf269d73
https://git.kernel.org/stable/c/3671a0775952026228ae44e096eb144bca75f8dc
https://git.kernel.org/stable/c/ab48dc0e23eb714b3f233f8e8f6deed7df2051f5
https://git.kernel.org/stable/c/f3b52167a0cb23b27414452fbc1278da2ee884fc
Powered by blists - more mailing lists