From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Cheng Yongkang <teel4res@gmail.com>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Jason Wang <jasowangio@gmail.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Petar Penkov <peterpenkov96@gmail.com>
Subject: Re: [PATCH net] net: tun: hold napi_mutex when deleting NAPI in tun_detach_all()
Date: Fri, 23 Oct 2026 19:24:33 -0400 [thread overview]
Message-ID: <willemdebruijn.kernel.2ec6aa9785f36@gmail.com> (raw)
In-Reply-To: <179268538303.70821.16548460883330758972@gmail.com>
Cheng Yongkang wrote:
> With IFF_NAPI_FRAGS, tun_get_user() takes tfile->napi_mutex, gets the
> skb from napi_get_frags() and copies the user data into it before it
> enters the RCU read-side section around napi_gro_frags().
>
> tun_detach_all() waits with synchronize_net() and then calls
> tun_napi_del() without napi_mutex. netif_napi_del() frees napi->skb
> through napi_free_frags(). A writer that is still copying has not yet
> entered its RCU section, so synchronize_net() does not wait for it, and
> deleting the device frees the skb while the writer is using it:
>
> BUG: KASAN: slab-use-after-free in skb_copy_datagram_from_iter+0x175/0x720
> Read of size 8 at addr ffff888077def990 by task br029-poc/9406
> Call Trace:
> skb_copy_datagram_from_iter+0x175/0x720
> tun_get_user+0xb42/0x3d00
> tun_chr_write_iter+0x113/0x200
> ...
> Freed by task 9405:
> kmem_cache_free+0x184/0x670
> __netif_napi_del_locked+0x2bb/0x3c0
> tun_net_uninit+0x566/0xa70
> unregister_netdevice_many_notify+0x1a26/0x2090
> rtnl_dellink+0x514/0x710
>
> __tun_detach() also calls tun_napi_del() without the mutex, but only
> from tun_chr_close(), when no write on that file can be in flight.
>
> Take napi_mutex around tun_napi_del() in tun_detach_all() for both
> attached and disabled queues.
>
> Fixes: 90e33d459407 ("tun: enable napi_gro_frags() for TUN/TAP driver")
> Assisted-by: LLM
> Signed-off-by: Cheng Yongkang <teel4res@gmail.com>
Reviewed-by: Willem de Bruijn <willemb@google.com>
prev parent reply other threads:[~2026-10-23 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 15:26 Cheng Yongkang
2026-10-23 23:24 ` Willem de Bruijn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=willemdebruijn.kernel.2ec6aa9785f36@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=jasowangio@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peterpenkov96@gmail.com \
--cc=teel4res@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®