CVE-2023-52702: net: openvswitch: fix possible memory leak in ovs_meter_cmd_set()
In the Linux kernel, the following vulnerability has been resolved:
net: openvswitch: fix possible memory leak in ovs_meter_cmd_set()
old_meter needs to be free after it is detached regardless of whether
the new meter is successfully attached.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can leak memory in the Open vSwitch meter update path. Memory leaks usually matter because repeated triggering can reduce system stability over time. The source bundle does not provide a CVSS score, affected distributions, proof of exploitation, or business-impact detail, so urgency depends on whether affected systems use Open vSwitch meter functionality.
Executive priority
Handle through normal kernel patch management, with higher priority for Open vSwitch infrastructure. There is no source-backed evidence of active exploitation or severity scoring, but kernel memory leaks can affect availability on exposed or heavily automated systems.
Technical view
The resolved kernel bug is in ovs_meter_cmd_set(). After detaching old_meter, the code needed to free it regardless of whether the new meter was attached successfully. The provided stable kernel references are the only fix evidence in the bundle; no exploit mechanics, CWE, or CVSS vector are provided.
Likely exposure
Most relevant exposure is Linux systems running affected kernel lines with Open vSwitch kernel functionality, especially where meter configuration is used. The bundle lists Linux kernel versions and stable commits but does not identify specific distributions, appliances, cloud images, or whether remote attackers can reach the affected path.
Exploitation context
The bundle does not support active exploitation: KEV is false and no cited source claims exploitation. The only described impact is a possible memory leak. Treat exploitability and attacker prerequisites as unconfirmed until vendor advisories or kernel analysis provide more detail.
Researcher notes
Evidence is limited to the CVE description and kernel stable commit references. Key missing details include trigger permissions, namespace constraints, remote reachability, practical impact, and fixed downstream package versions. Avoid claiming denial-of-service or exploitation without additional vendor or kernel analysis.
Mitigation direction
Update affected Linux kernels to vendor builds containing the referenced stable fixes.
Prioritize systems using Open vSwitch or network virtualization features.
Check Linux distribution advisories for backported fixes and exact package versions.
Monitor affected hosts for abnormal kernel memory pressure until patched.
Validation and detection
Inventory kernel versions against the affected versions listed in the CVE bundle.
Identify hosts using Open vSwitch and meter configuration features.
Confirm the relevant stable fix commit or vendor backport is present.
Review distribution security notes for package-specific fixed versions.
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-2023-52702 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.