VDB

CVE-2025-68169

CVE-2025-68169 PUBLISHED

netpoll: Fix deadlock in memory allocation under spinlock

Reported by linux · Published December 16, 2025

In the Linux kernel, the following vulnerability has been resolved: netpoll: Fix deadlock in memory allocation under spinlock Fix a AA deadlock in refill_skbs() where memory allocation while holding skb_pool->lock can trigger a recursive lock acquisition attempt. The deadlock scenario occurs when the system is under severe memory pressure: 1. refill_skbs() acquires skb_pool->lock (spinlock) 2. alloc_skb() is called while holding the lock 3. Memory allocator fails and calls slab_out_of_memory() 4. This triggers printk() for the OOM warning 5. The console output path calls netpoll_send_udp() 6. netpoll_send_udp() attempts to acquire the same skb_pool->lock 7. Deadlock: the lock is already held by the same CPU Call stack: refill_skbs() spin_lock_irqsave(&skb_pool->lock) <- lock acquired __alloc_skb() kmem_cache_alloc_node_noprof() slab_out_of_memory() printk() console_flush_all() netpoll_send_udp() skb_dequeue() spin_lock_irqsave(&skb_pool->lock) <- deadlock attempt This bug was exposed by commit 248f6571fd4c51 ("netpoll: Optimize skb refilling on critical path") which removed refill_skbs() from the critical path (where nested printk was being deferred), letting nested printk being called from inside refill_skbs() Refactor refill_skbs() to never allocate memory while holding the spinlock. Another possible solution to fix this problem is protecting the refill_skbs() from nested printks, basically calling printk_deferred_{enter,exit}() in refill_skbs(), then, any nested pr_warn() would be deferred. I prefer this approach, given I _think_ it might be a good idea to move the alloc_skb() from GFP_ATOMIC to GFP_KERNEL in the future, so, having the alloc_skb() outside of the lock will be necessary step. There is a possible TOCTOU issue when checking for the pool length, and queueing the new allocated skb, but, this is not an issue, given that an extra SKB in the pool is harmless and it will be eventually used.

EPSS 0.19% · 8.3th percentile

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
LinuxLinux327c20c21d80e0d87834b392d83ae73c955ad8ff, 06742a3ab884d7428c9050b205ffcf6a8a548397

Risk scores

EPSS Score
0.19%
8.3th percentile

Affected products

VendorProductVersions
LinuxLinux248f6571fd4c51531f7f8f07f186f7ae98a50afc, 248f6571fd4c51531f7f8f07f186f7ae98a50afc
LinuxLinux6.15, 0, 6.17.8
LinuxLinux6.17.8, 0, 6.18
linuxlinux_kernel6.15, 6.15

Timeline

  • Dec 16, 2025 CVE Published
  • Dec 17, 2025 EPSS Score (30 in total, the first dated here)
  • Mar 26, 2026 Coalition ESS Score (2 in total, the first dated here)
  • Mar 29, 2026 Distribution Patch (186 in total, the first dated here)
  • Mar 29, 2026 Security Advisory (192 in total, the first dated here)

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-68169
vulnetix vdb fixes CVE-2025-68169

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-68169/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›