page_pool: always add GFP_NOWARN for ATOMIC allocations
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.15.197, 6.1.159, 6.6.117, 6.12.58, 6.17.8
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From ff7d6b27f894f1469dc51ccb828b7363ccd9799f · fixed in 0ec2cd5c58793d0c622797cd5fbe26634b357210; From ff7d6b27f894f1469dc51ccb828b7363ccd9799f · fixed in 9835a0fd59a1df5ec0740fdab6d50db68e0f10de; From ff7d6b27f894f1469dc51ccb828b7363ccd9799f · fixed in 7613c06ffa89c1e2266fb532e23ef7dfdf269d73; From ff7d6b27f894f1469dc51ccb828b7363ccd9799f · fixed in 3671a0775952026228ae44e096eb144bca75f8dc; From ff7d6b27f894f1469dc51ccb828b7363ccd9799f · fixed in ab48dc0e23eb714b3f233f8e8f6deed7df2051f5; From ff7d6b27f894f1469dc51ccb828b7363ccd9799f · fixed in f3b52167a0cb23b27414452fbc1278da2ee884fc
- Linux Linux
4.18
- KernelLinux
From 4.18.0 · fixed in 5.15.197; From 5.16.0 · fixed in 6.1.159; From 6.2.0 · fixed in 6.6.117; From 6.7.0 · fixed in 6.12.58; From 6.13.0 · fixed in 6.17.8