Netdev List
 help / color / mirror / Atom feed
From: Ilya Maximets <i.maximets@ovn.org>
To: Ren Wei <enjou1224z@gmail.com>,
	netdev@vger.kernel.org, dev@openvswitch.org
Cc: aconole@redhat.com, echaudro@redhat.com, davem@davemloft.net,
	edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
	yihung.wei@gmail.com, vega@nebusec.ai, tonanli66@gmail.com,
	xuyuqiabc@gmail.com, Ilya Maximets <i.maximets@ovn.org>
Subject: Re: [PATCH net v2 1/1] openvswitch: Fix CT limit teardown use-after-free
Date: Mon, 3 Aug 2026 14:25:07 +0200	[thread overview]
Message-ID: <0544fde9-55a4-4345-bc85-e0fba6e16195@ovn.org> (raw)
In-Reply-To: <b4779996-0453-442c-a92f-1312418b73bb@ovn.org>

On 7/22/26 11:19 PM, Ilya Maximets wrote:
> On 7/22/26 10:59 PM, Ilya Maximets wrote:
>> On 7/22/26 6:40 PM, Ren Wei wrote:
>>> From: Yuqi Xu <xuyuqiabc@gmail.com>
>>>
>>> Packet processing uses CT limit state under RCU, while netns teardown
>>> frees that state under ovs_mutex. The CT limit pointer was neither removed
>>> from readers nor protected by a grace period, allowing packet processing to
>>> dereference the freed state.
>>>
>>> Replace the pointer before freeing the CT limit state. Wait for in-flight
>>> RCU readers before freeing its contents. Serialize CT limit netlink
>>> operations with teardown for the full lifetime of their state accesses.
>>>
>>> Fixes: 11efd5cb04a1 ("openvswitch: Support conntrack zone limit")
>>> Cc: stable@vger.kernel.org
>>> Reported-by: Vega <vega@nebusec.ai>
>>> Assisted-by: Codex:GPT-5.4
>>> Co-developed-by: Nan Li <tonanli66@gmail.com>
>>> Signed-off-by: Nan Li <tonanli66@gmail.com>
>>> Signed-off-by: Yuqi Xu <xuyuqiabc@gmail.com>
>>> Signed-off-by: Ren Wei <enjou1224z@gmail.com>
>>> ---
Hi.  It's been silent here for a while.  Do you plan to send a new version
of this fix, or should someone else take it over?

Best regards, Ilya Maximets.

      reply	other threads:[~2026-08-03 12:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22 16:40 [PATCH net v2 0/1] openvswitch: Fix CT limit teardown use-after-free Ren Wei
2026-07-22 16:40 ` [PATCH net v2 1/1] " Ren Wei
2026-07-22 20:59   ` Ilya Maximets
2026-07-22 21:19     ` Ilya Maximets
2026-08-03 12:25       ` Ilya Maximets [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=0544fde9-55a4-4345-bc85-e0fba6e16195@ovn.org \
    --to=i.maximets@ovn.org \
    --cc=aconole@redhat.com \
    --cc=davem@davemloft.net \
    --cc=dev@openvswitch.org \
    --cc=echaudro@redhat.com \
    --cc=edumazet@google.com \
    --cc=enjou1224z@gmail.com \
    --cc=horms@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=tonanli66@gmail.com \
    --cc=vega@nebusec.ai \
    --cc=xuyuqiabc@gmail.com \
    --cc=yihung.wei@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