Process crash via stale RAW_ENCAP pointer
Published Jul 20, 2021 · Updated May 5, 2025
Use-after-free in Open vSwitch 2.11.0 through 2.15.0 allows local users to crash a decoding process via a crafted RAW_ENCAP action. In decode_NXAST_RAW_ENCAP, decode_ed_prop() can reallocate the output buffer, but the decoder retains the old encap pointer and writes through freed memory. Triggering the crash requires local processing of the crafted action with user interaction; the published impact is limited to service interruption.
Summary
What happened
Use-after-free in Open vSwitch 2.11.0 through 2.15.0 allows local users to crash a decoding process via a crafted RAW_ENCAP action. In decode_NXAST_RAW_ENCAP, decode_ed_prop() can reallocate the output buffer, but the decoder retains the old encap pointer and writes through freed memory. Triggering the crash requires local processing of the crafted action with user interaction; the published impact is limited to service interruption.
The record
- CVE
- CVE-2021-36980
- Published
- Jul 20, 2021
- Updated
- May 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 20, 2021CVE publishedPublication date reported by the CVE source.
- May 5, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo