net: serialize netif_running() check in enqueue_to_backlog()
Subsystems (2)
PATCH 1/1 net: serialize netif_running() check in enqueue_to_backlog()
Syzbot reported a KASAN slab-use-after-free in fib_rules_lookup().
The root cause is a race condition where packets can escape the backlog flushing during device unregistration (e.g., during netns exit).
Commit e9e4dd3267d0 ("net: do not process device backlog during unregistration") introduced a lockless netif_running() check in enqueue_to_backlog() to prevent queuing packets to an unregistering device.
However, this creates a TOCTOU race window.
A lockless transmitter (like veth_xmit) can pass
the check before dev_close() clears IFF_UP. If the transmitter is then delayed, flush_all_backlogs() can run and finish before the transmitter grabs the backlog lock and queues the packet. The packet then escapes the flush and triggers UAF later when processed.
Fix this by moving the netif_running() check inside the backlog lock. This serializes the check with the flush work (which also grabs the lock). We then either queue the packet before the flush runs (so it gets flushed), or check netif_running() after the flush/close completes (so it gets dropped).
--- net/core/dev.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
net/core/dev.c +4 -2
@@ -5381,8 +5381,6 @@ static int enqueue_to_backlog(struct sk_buff *skb, int cpu,u32 tail; reason =SKB_DROP_REASON_DEV_READY ; -if (unlikely (!netif_running (skb->dev))) - goto bad_dev; sd = &per_cpu (softnet_data, cpu);
@@ -5394,6 +5392,10 @@ static int enqueue_to_backlog(struct sk_buff *skb, int cpu,backlog_lock_irq_save (sd, &flags); qlen =skb_queue_len (&sd->input_pkt_queue);if (likely (qlen <= max_backlog)) { +if (unlikely (!netif_running (skb->dev))) { +backlog_unlock_irq_restore (sd, flags); + goto bad_dev; + }if (!qlen) {/* Schedule NAPI for backlog device. We can use * non atomic operation as we own the queue lock.
Signature · 1 line
2.54.0.1189.g8c84645362-goog
Quoted 23 lines · Eric Dumazet
Syzbot reported a KASAN slab-use-after-free in
fib_rules_lookup().The root cause is a race condition where packets can escape the backlog flushing during device unregistration (e.g., during netns exit).
Commit
e9e4dd3267d0("net: do not process device backlog during unregistration") introduced a locklessnetif_running()check inenqueue_to_backlog()to prevent queuing packets to an unregistering device.However, this creates a TOCTOU race window.
A lockless transmitter (like
veth_xmit) can pass
the check beforedev_close()clearsIFF_UP. If the transmitter is then delayed,flush_all_backlogs()can run and finish before the transmitter grabs the backlog lock and queues the packet. The packet then escapes the flush and triggers UAF later when processed.Fix this by moving the
netif_running()check inside the backlog lock. This serializes the check with the flush work (which also grabs the lock). We then either queue the packet before the flush runs (so it gets flushed), or checknetif_running()after the flush/close completes (so it gets dropped).
Quoted 4 lines
Fixes e9e4dd3267d0 ("net: do not process device backlog during unregistration")Reported-by [email protected]Signed-off-by Eric Dumazet <[email protected]>
Thanks for catching this !
This patch was applied to netdev/net-next.git (main) by Jakub Kicinski <[email protected]>:
Hello:
This patch was applied to netdev/net-next.git (main) by Jakub Kicinski <[email protected]>:
Quoted 10 lines · On Tue, 16 Jun 2026 14:13:17 +0000 you wrote:
Syzbot reported a KASAN slab-use-after-free in
fib_rules_lookup().The root cause is a race condition where packets can escape the backlog flushing during device unregistration (e.g., during netns exit).
Commit
e9e4dd3267d0("net: do not process device backlog during unregistration") introduced a locklessnetif_running()check inenqueue_to_backlog()to prevent queuing packets to an unregistering device.[...]
Here is the summary with links:
- [net] net: serialize netif_running() check in enqueue_to_backlog()
https://git.kernel.org/netdev/net-next/c/46762cefe7f4
You are awesome, thank you!
Signature · 2 lines
Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html