All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qihang <q.h.hack.winter@gmail.com>
To: netdev@vger.kernel.org
Cc: steffen.klassert@secunet.com, herbert@gondor.apana.org.au
Subject: [PATCH net 0/2] vti: fix tunnel device use-after-free across async crypto resumption
Date: Wed, 30 Sep 2026 17:08:10 +0800	[thread overview]
Message-ID: <20260930090813.73901-1-q.h.hack.winter@gmail.com> (raw)

vti_input() and vti6_input_proto() cache the tunnel pointer in the skb
control buffer without taking a reference.  With async crypto the
receive callback runs from the crypto completion, so a concurrent
RTM_DELLINK can free the tunnel device before the callback uses the
cached pointer.  The existing rcu_read_lock() around the callback does
not protect it.

Patch 1 fixes the IPv4 side and carries the full description; patch 2
applies the same fix to the IPv6 side.

Qihang (2):
  vti: fix tunnel device use-after-free across async crypto resumption
  vti6: fix tunnel device use-after-free across async crypto resumption

 net/ipv4/ip_vti.c  | 7 +++++++
 net/ipv6/ip6_vti.c | 8 ++++++++
 2 files changed, 15 insertions(+)

-- 
2.54.0 (Apple Git-157)


             reply	other threads:[~2026-09-30  9:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30  9:08 Qihang [this message]
2026-09-30  9:08 ` [PATCH net 1/2] vti: fix tunnel device use-after-free across async crypto resumption Qihang
2026-10-04 10:08   ` netdev-bot+sashiko
2026-10-08  1:49     ` Qihang
2026-10-12  7:54       ` Steffen Klassert
2026-10-12  9:07         ` Qihang
2026-10-12 10:13           ` Steffen Klassert
2026-10-12 11:21             ` Qihang
2026-10-12 11:25               ` Steffen Klassert
2026-09-30  9:08 ` [PATCH net 2/2] vti6: " Qihang
2026-10-04 10:08   ` netdev-bot+sashiko
2026-09-30  9:13 ` [PATCH net 0/2] vti: " netdev-bot+sinfo

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=20260930090813.73901-1-q.h.hack.winter@gmail.com \
    --to=q.h.hack.winter@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=steffen.klassert@secunet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.