From: Antonio Quartulli <antonio@openvpn.net>
To: netdev@vger.kernel.org, kuba@kernel.org
Cc: ralf@mandelbit.com, Hyunwoo Kim <imv4bel@gmail.com>,
Sabrina Dubroca <sd@queasysnail.net>
Subject: Re: [RFC net] ovpn: fix race between deleting interface and adding new peer
Date: Tue, 5 May 2026 21:20:16 +0200 [thread overview]
Message-ID: <92b24c57-ccc6-45db-99db-31596ba3f5d3@openvpn.net> (raw)
In-Reply-To: <20260504142033.2327646-1-antonio@openvpn.net>
On 04/05/2026 16:20, Antonio Quartulli wrote:
> This patch is sent as RFC to give the AI a chance to review it once
> again, since it was able to spot a new race condition in its
> previous version.
So we got a "critical" report from sashiko-gemini.
The AI analyzed what happens along the error path, by backtracking all
callers and checking for potential problems.
It found a potential UAF due to a worker not being disabled when
free'ing the peer in this early stage.
The analysis seems sound and I will deepen it.
However, this bug is not introduced by this patch.
It just happened that sashiko investigated the error path due to this
patch introducing a "return -ENODEV".
But the problem existed before because we have other spots where an
error can be returned.
For this reason this patch now seems to be ok and to cover all issues we
have found so far.
Once my outstanding PR for net is merged, I will send a new one with
this fix (and maybe the UAF fix too).
Thanks a lot.
Regards,
--
Antonio Quartulli
OpenVPN Inc.
prev parent reply other threads:[~2026-05-05 19:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 14:20 [RFC net] ovpn: fix race between deleting interface and adding new peer Antonio Quartulli
2026-05-04 23:54 ` Jakub Kicinski
2026-05-05 0:04 ` Antonio Quartulli
2026-05-05 8:07 ` Roman Gushchin
2026-05-05 19:20 ` Antonio Quartulli [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=92b24c57-ccc6-45db-99db-31596ba3f5d3@openvpn.net \
--to=antonio@openvpn.net \
--cc=imv4bel@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ralf@mandelbit.com \
--cc=sd@queasysnail.net \
/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