Openvswitch: Stack Out-of-Bounds Read Vulnerability

Kernel Updated 02 Oct 2025

Summary

31/05/2021
N/A
No i
Unrated
Not published

UVI-2021-1000072: openvswitch: fix stack OOB read while fragmenting IPv4 packets. Affects Kernel versions >= d52e5a7e7ca49457dd31fc8b42fb7c0d58a31221, < b3502b04e84ac5349be95fc033c17bd701d2787a. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Openvswitch is a software-based virtual switch that is commonly used in virtualized environments. It provides network connectivity and switching capabilities for virtual machines. The vulnerability in Openvswitch affects the fragmentation of IPv4 packets, leading to a stack out-of-bounds read. This vulnerability can potentially be exploited by an attacker to gain unauthorized access or cause a denial-of-service condition.

Vulnerability Detail

The vulnerability in Openvswitch arises from a stack out-of-bounds read while fragmenting IPv4 packets. This can occur when processing specially crafted packets, leading to the potential disclosure of sensitive information or a system crash. The vulnerability was introduced in version v4.16 of the Linux Kernel and is fixed in version v5.12.3. It is important to note that the actual impact and attack feasibility of this vulnerability have not been proven.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a workaround, if updating the Linux Kernel is not immediately feasible, network administrators can consider implementing additional security measures such as network segmentation, access control lists, and traffic filtering to mitigate the risk of exploitation. However, applying the official patch by updating the Linux Kernel is the recommended solution.

Conclusion

The stack out-of-bounds read vulnerability in Openvswitch while fragmenting IPv4 packets can pose a significant risk to the security and stability of virtualized environments. It is crucial to promptly update the Linux Kernel to version v5.12.3 or later to mitigate this vulnerability. For further support and assistance in vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

Openvswitch is a software-based virtual switch used in virtualized environments to provide network connectivity and switching capabilities for virtual machines.

This vulnerability in Openvswitch can potentially allow an attacker to gain unauthorized access or cause a denial-of-service condition.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.12.3 or later, which includes the necessary patch to address the issue.

As a workaround, network administrators can implement additional security measures such as network segmentation, access control lists, and traffic filtering to mitigate the risk of exploitation.

For more information about this vulnerability, you can refer to the official references provided in the vulnerability details section.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback