From: Steffen Klassert <steffen.klassert@secunet.com>
To: syzbot <syzbot@kernel.org>
Cc: <syzkaller-bugs@googlegroups.com>,
Aleksandr Nogikh <nogikh@google.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Jakub Kicinski <kuba@kernel.org>, <netdev@vger.kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Antony Antony <antony.antony@secunet.com>, <horms@kernel.org>,
<linux-kernel@vger.kernel.org>, <syzbot@lists.linux.dev>
Subject: Re: [PATCH] xfrm: add missing RCU read lock in xfrm_send_migrate_state()
Date: Mon, 24 Aug 2026 07:01:33 +0200 [thread overview]
Message-ID: <aovQLX1EsvRQOjWQ@secunet.com> (raw)
In-Reply-To: <2f866679-25c2-4b17-9fa6-086d4c3b593f@mail.kernel.org>
On Fri, Jul 31, 2026 at 10:06:20AM +0000, syzbot wrote:
> From: Aleksandr Nogikh <nogikh@google.com>
>
> xfrm_nlmsg_multicast() requires the RCU read lock to be held because it
> safely dereferences the net->xfrm.nlsk pointer using rcu_dereference().
> When it is called from xfrm_send_migrate_state(), the RCU read lock is not
> held, which triggers a suspicious RCU usage warning:
>
> WARNING: suspicious RCU usage
> net/xfrm/xfrm_user.c:1630 suspicious rcu_dereference_check() usage!
>
> Call Trace:
> lockdep_rcu_suspicious+0x13f/0x1d0 kernel/locking/lockdep.c:6876
> xfrm_nlmsg_multicast+0x1d8/0x1f0 net/xfrm/xfrm_user.c:1630
> xfrm_send_migrate_state+0x870/0xae0 net/xfrm/xfrm_user.c:3340
> xfrm_do_migrate_state+0x1749/0x1e90 net/xfrm/xfrm_user.c:3507
> xfrm_user_rcv_msg+0x7a8/0xf30 net/xfrm/xfrm_user.c:3907
>
> Fix this by wrapping the xfrm_nlmsg_multicast() call in
> xfrm_send_migrate_state() with rcu_read_lock() and rcu_read_unlock().
>
> Fixes: a9d155ea9b44 ("xfrm: add XFRM_MSG_MIGRATE_STATE for single SA migration")
> Assisted-by: Gemini:gemini-3.5-flash Gemini:gemini-3.1-pro-preview syzbot
> Reported-by: syzbot+c0e99a1aa85a286d7a3b@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=c0e99a1aa85a286d7a3b
> Link: https://syzkaller.appspot.com/ai_job?id=8977f559-3a7e-4bb5-b4d6-1196956260b6
> Signed-off-by: Aleksandr Nogikh <nogikh@google.com>
Applied, thanks a lot!
prev parent reply other threads:[~2026-08-24 5:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 10:06 [PATCH] xfrm: add missing RCU read lock in xfrm_send_migrate_state() syzbot
2026-08-24 5:01 ` Steffen Klassert [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=aovQLX1EsvRQOjWQ@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=antony.antony@secunet.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nogikh@google.com \
--cc=pabeni@redhat.com \
--cc=syzbot@kernel.org \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.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