CVE-2023-52977

net: openvswitch: fix flow memory leak in ovs_flow_cmd_new

MEDIUM

5.5

CVSS Score

Published: March 27, 2025 at 04:43 PM UTC

Updated: June 17, 2026 at 06:44 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.3%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: fix flow memory leak in ovs_flow_cmd_new Syzkaller reports a memory leak of new_flow in ovs_flow_cmd_new() as it is not freed when an allocation of a key fails. BUG: memory leak unreferenced object 0xffff888116668000 (size 632): comm "syz-executor231", pid 1090, jiffies 4294844701 (age 18.871s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<00000000defa3494>] kmem_cache_zalloc include/linux/slab.h:654 [inline] [<00000000defa3494>] ovs_flow_alloc+0x19/0x180 net/openvswitch/flow_table.c:77 [<00000000c67d8873>] ovs_flow_cmd_new+0x1de/0xd40 net/openvswitch/datapath.c:957 [<0000000010a539a8>] genl_family_rcv_msg_doit+0x22d/0x330 net/netlink/genetlink.c:739 [<00000000dff3302d>] genl_family_rcv_msg net/netlink/genetlink.c:783 [inline] [<00000000dff3302d>] genl_rcv_msg+0x328/0x590 net/netlink/genetlink.c:800 [<000000000286dd87>] netlink_rcv_skb+0x153/0x430 net/netlink/af_netlink.c:2515 [<0000000061fed410>] genl_rcv+0x24/0x40 net/netlink/genetlink.c:811 [<000000009dc0f111>] netlink_unicast_kernel net/netlink/af_netlink.c:1313 [inline] [<000000009dc0f111>] netlink_unicast+0x545/0x7f0 net/netlink/af_netlink.c:1339 [<000000004a5ee816>] netlink_sendmsg+0x8e7/0xde0 net/netlink/af_netlink.c:1934 [<00000000482b476f>] sock_sendmsg_nosec net/socket.c:651 [inline] [<00000000482b476f>] sock_sendmsg+0x152/0x190 net/socket.c:671 [<00000000698574ba>] ____sys_sendmsg+0x70a/0x870 net/socket.c:2356 [<00000000d28d9e11>] ___sys_sendmsg+0xf3/0x170 net/socket.c:2410 [<0000000083ba9120>] __sys_sendmsg+0xe5/0x1b0 net/socket.c:2439 [<00000000c00628f8>] do_syscall_64+0x30/0x40 arch/x86/entry/common.c:46 [<000000004abfdcf4>] entry_SYSCALL_64_after_hwframe+0x61/0xc6 To fix this the patch rearranges the goto labels to reflect the order of object allocations and adds appropriate goto statements on the error paths. Found by Linux Verification Center (linuxtesting.org) with Syzkaller.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v ≥ 4.9.337v ≥ 6.0.164.14.303 ≤ v < 4.14.3064.19.270 ≤ v < 4.19.2734.9.337 ≤ v < 4.105.10.163 ≤ v < 5.10.1685.15.86 ≤ v < 5.15.935.4.229 ≤ v < 5.4.2326.0.16 ≤ v < 6.16.1.2 ≤ v < 6.1.11133615a6007684df648feb9d327714e399afd432d5fa5bdccec2361fc6c4ed05a7367155b3a1e94.14.303 4.19.270 4.9.3374f592e712ea2132f511d545954867d7880df5be25.10.163 5.15.86 5.4.229 6.0.16 6.1.2655e873bf528f0f46ce6b069f9a2daee9621197c6736b61ecf230dd656464de0f514bdeadb384f2068bb10101e6b0a6bb44e9c908ef795fc4af99eae8b74211bf60b3e0c0ed4fe3d16c92ffdcaaf34eba991a411c3e21ef22507400dbb179ae02029d42cee27d70556a47c3a07e65a60f47e3ea12a255af8

Vendor states this is fixed in 0c598aed445eb45b0ee7ba405f7ece99ee349c30 (fixed)

Vendor states this is fixed in 1ac653cf886cdfc082708c82dc6ac6115cebd2ee (fixed)

Vendor states this is fixed in 70154489f531587996f3e9d7cceeee65cff0001d (fixed)

Vendor states this is fixed in 70d40674a549d498bd63d5432acf46205da1534b (fixed)

Vendor states this is fixed in af4e720bc00a2653f7b9df21755b9978b3d7f386 (fixed)

Vendor states this is fixed in ed6c5e8caf55778500202775167e8ccdb1a030cb (fixed)

Vendor states this is fixed in f423c2efd51d7eb1d143c2be7eea233241d9bbbf (fixed)

Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.14.306, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.19.273, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.10.168, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.15.93, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.4.232, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.1.11, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references