Threats Tagged 'cve-2025-68321'
View all threats tagged with 'cve-2025-68321'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2025-68321'
Click on any threat for detailed analysis and mitigation recommendations
A vulnerability in the Linux kernel related to the page_pool subsystem has been resolved. The issue involved the lack of the GFP_NOWARN flag for ATOMIC page allocations, which driver authors often omit. This omission can cause unnecessary warnings during out-of-memory (OOM) conditions, particularly affecting network receive (Rx) paths. The fix ensures that page_pool adds GFP_NOWARN by default for ATOMIC allocations to prevent these warnings. Join the discussion | GCVE Database | 12/16/2025, 18:31:34 UTC Added: 07/30/2026, 15:50:42 UTC |
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. Join the discussion | GCVE Database | 12/16/2025, 16:16:00 UTC Added: 07/18/2026, 11:32:57 UTC |
Showing 1 to 2 of 2 results