LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49959: openvswitch: fix memory leak at failed datapath creation

In the Linux kernel, the following vulnerability has been resolved: openvswitch: fix memory leak at failed datapath creation ovs_dp_cmd_new()->ovs_dp_change()->ovs_dp_set_upcall_portids() allocates array via kmalloc. If for some reason new_vport() fails during ovs_dp_cmd_new() dp->upcall_portids must be freed. Add missing kfree. Kmemleak example: unreferenced object 0xffff88800c382500 (size 64): comm "dump_state", pid 323, jiffies 4294955418 (age 104.347s) hex dump (first 32 bytes): 5e c2 79 e4 1f 7a 38 c7 09 21 38 0c 80 88 ff ff ^.y..z8..!8..... 03 00 00 00 0a 00 00 00 14 00 00 00 28 00 00 00 ............(... backtrace: [<0000000071bebc9f>] ovs_dp_set_upcall_portids+0x38/0xa0 [<000000000187d8bd>] ovs_dp_change+0x63/0xe0 [<000000002397e446>] ovs_dp_cmd_new+0x1f0/0x380 [<00000000aa06f36e>] genl_family_rcv_msg_doit+0xea/0x150 [<000000008f583bc4>] genl_rcv_msg+0xdc/0x1e0 [<00000000fa10e377>] netlink_rcv_skb+0x50/0x100 [<000000004959cece>] genl_rcv+0x24/0x40 [<000000004699ac7f>] netlink_unicast+0x23e/0x360 [<00000000c153573e>] netlink_sendmsg+0x24e/0x4b0 [<000000006f4aa380>] sock_sendmsg+0x62/0x70 [<00000000d0068654>] ____sys_sendmsg+0x230/0x270 [<0000000012dacf7d>] ___sys_sendmsg+0x88/0xd0 [<0000000011776020>] __sys_sendmsg+0x59/0xa0 [<000000002e8f2dc1>] do_syscall_64+0x3b/0x90 [<000000003243e7cb>] entry_SYSCALL_64_after_hwframe+0x63/0xcd

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a memory leak in the Open vSwitch datapath creation path. If datapath creation fails, a small allocated array may not be freed. The sources do not show active exploitation, CVSS scoring, or a vendor advisory beyond kernel fix references.

Executive priority

Handle as targeted kernel maintenance, not an emergency based on the supplied evidence. Raise priority for infrastructure that relies on Open vSwitch in production because resource leaks can affect availability if repeatedly triggered.

Technical view

ovs_dp_cmd_new() calls ovs_dp_change(), which can allocate dp->upcall_portids through ovs_dp_set_upcall_portids(). If new_vport() later fails, dp->upcall_portids was not freed. The referenced fix adds the missing kfree path.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with Open vSwitch datapath creation reachable. The bundle lists Linux kernel 5.15, 5.15.66, 5.19.8, and 6.0 as affected, but package-level distribution mapping is not provided.

Exploitation context

The source bundle does not cite public exploitation, CISA KEV inclusion, exploit code, or real-world attacks. The practical impact is most likely resource leakage during failed datapath creation, but attack prerequisites and repeatability are not established in the supplied evidence.

Researcher notes

The record provides a narrow kernel memory-management bug and three upstream stable references. It lacks CVSS, CWE, distro package status, exploitability analysis, and clear privilege requirements. Validate against actual downstream kernels before declaring exposure.

Mitigation direction

  • Check your Linux vendor advisory for a kernel build containing the referenced stable fixes.
  • Prioritize hosts using Open vSwitch or network virtualization features for kernel update review.
  • Apply tested vendor kernel updates through normal change control.
  • Monitor kernel memory behavior on exposed Open vSwitch hosts until patched.

Validation and detection

  • Inventory kernel versions on systems using Open vSwitch.
  • Confirm whether vendor kernel changelogs include the referenced upstream fix commits.
  • Review Open vSwitch usage on virtualization, container networking, and SDN hosts.
  • Check operational monitoring for unexplained kernel memory growth on relevant systems.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-49959 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb83d23a2a38b1770da0491257ae81d52307f7816, b83d23a2a38b1770da0491257ae81d52307f7816, b83d23a2a38b1770da0491257ae81d52307f7816unaffected
LinuxLinux5.15, 0, 5.15.66, 5.19.8, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.