CVE-2022-32166 | ovs - buffer over-read

In ovs versions v0.90.0 through v2.5.0 are vulnerable to heap buffer over-read in flow.c. An unsafe comparison of “minimasks” function could lead access to an unmapped region of memory. This vulnerability is capable of crashing the software, memory modification, and possible remote execution.

Published: 2022-09-28 Last update: 2025-05-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-32166 is rated Moderate Risk (53.2/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 1.66%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-32166

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-06 1.75% 1.66% -0.09%
2 2026-06-04 0.65% 1.75% +1.10%
3 2026-05-24 — 0.65% —

Full EPSS history (20 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-32166

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.1 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 4.2 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2022-32166

OS Trackers for CVE-2022-32166

vendor priority summary link
debian not yet assigned CVE-2022-32166 not yet assigned priority: Debian including 1 source packages (openvswitch), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-32166
redhat high — https://access.redhat.com/security/cve/CVE-2022-32166
suse medium CVE-2022-32166 severity moderate: SUSE including 34 source package names (libdpdk-18_11-18.11.9-150100.4.23.1, libopenvswitch-2_11-0-2.11.5-150100.3.18.2, …), 286 product×package rows across 37 product lines (SUSE Enterprise Storage 7, SUSE Enterprise Storage 7.1, … (37 product lines)): Known Not Affected 232, Fixed 54. https://www.suse.com/security/cve/CVE-2022-32166/
ubuntu medium CVE-2022-32166 medium priority: Ubuntu including 1 source packages (openvswitch), 7 status rows across 7 suites (bionic, focal, jammy, kinetic, trusty, upstream, xenial): not-affected 3, released 2, ignored 1, needs-triage 1. https://ubuntu.com/security/CVE-2022-32166

Affected software / configurations for CVE-2022-32166

Vendor Product Version Raw CPE
cloudbase open_vswitch >= 0.90.0, <= 2.5.0 cpe:2.3:a:cloudbase:open_vswitch:*:*:*:*:*:*:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*

References for CVE-2022-32166

cvelogic Threat Intelligence