From: Eelco Chaudron <echaudro@redhat.com>
To: Ilya Maximets <i.maximets@ovn.org>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Tonghao Zhang <xiangxia.m.yue@gmail.com>,
Aaron Conole <aconole@redhat.com>,
dev@openvswitch.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net] net: openvswitch: fix potential UAF on meter attach failure
Date: Mon, 27 Jul 2026 16:28:46 +0200 [thread overview]
Message-ID: <5EB5E9EA-2E4F-4226-993A-142C79A6DF00@redhat.com> (raw)
In-Reply-To: <20260727121022.198461-1-i.maximets@ovn.org>
On 27 Jul 2026, at 14:10, Ilya Maximets wrote:
> While attaching a newly created meter attach_meter() function makes
> the new meter visible to other CPUs but can still fail afterwards.
> On failure, it detaches the meter back and returns an error.
>
> However, this is an unexpected behavior for the ovs_meter_cmd_set()
> that uses a plain kfree(meter) on attach failure without waiting for
> RCU readers to stop using it, assuming it was never visible.
>
> This is never a problem for ovs-vswitchd as it always creates meters
> before creating any flows that use them. But the UAF can be triggered
> with a custom application using uAPI:
>
> BUG: KASAN: slab-use-after-free in ovs_meter_execute (net/openvswitch/meter.c:653)
> Read of size 8 at addr ffff88810d152650 by task meter/2508
>
> Call Trace:
> ovs_meter_execute (net/openvswitch/meter.c:653)
> do_execute_actions (net/openvswitch/actions.c:1407)
> ovs_execute_actions (net/openvswitch/actions.c:1584)
> ovs_packet_cmd_execute (net/openvswitch/datapath.c:703)
> ...
> netlink_sendmsg (af_netlink.c:1900)
>
> Allocated by task 2519:
> __kasan_kmalloc (mm/kasan/common.c:398 mm/kasan/common.c:415)
> ovs_meter_cmd_set (net/openvswitch/meter.c:422)
> ...
> netlink_sendmsg (af_netlink.c:1900)
>
> Freed by task 2519:
> kfree (mm/slub.c:2705 mm/slub.c:6405 mm/slub.c:6720)
> ovs_meter_cmd_set (net/openvswitch/meter.c:479)
> ...
> netlink_sendmsg (af_netlink.c:1900)
>
> Fix that by making sure attach_meter() doesn't make the meter visible
> until all the checks are done and the function can't fail anymore.
>
> This also makes sure the "hash" value is calculated after the potential
> re-sizing of the table.
>
> Reported by Trend Micro's Zero Day Initiative as ZDI-CAN-31642.
>
> Fixes: c7c4c44c9a95 ("net: openvswitch: expand the meters supported number")
> Cc: stable@vger.kernel.org
> Signed-off-by: Ilya Maximets <i.maximets@ovn.org>
Thanks, Ilya, for looking into this. The patch looks good to me.
Reviewed-by: Eelco Chaudron <echaudro@redhat.com>
next prev parent reply other threads:[~2026-07-27 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 12:10 [PATCH net] net: openvswitch: fix potential UAF on meter attach failure Ilya Maximets
2026-07-27 14:28 ` Eelco Chaudron [this message]
2026-07-28 14:00 ` Ilya Maximets
2026-07-30 11:30 ` patchwork-bot+netdevbpf
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=5EB5E9EA-2E4F-4226-993A-142C79A6DF00@redhat.com \
--to=echaudro@redhat.com \
--cc=aconole@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=horms@kernel.org \
--cc=i.maximets@ovn.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=xiangxia.m.yue@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