page_pool: always add GFP_NOWARN for ATOMIC allocations
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ff7d6b27f894f1469dc51ccb828b7363ccd9799f · < ab48dc0e23eb714b3f233f8e8f6deed7df2051f5| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's page_pool did not always add GFP_NOWARN to ATOMIC page allocations. During out-of-memory conditions, network receive allocations can fail and produce warnings; the input does not describe an attacker action, authentication requirement, or user interaction.
Engineers running Linux kernels with page_pool should check their kernel version; affected versions are not specified.