Service interruption via failed pcap file open
Published Jan 19, 2024 · Updated Jun 2, 2025
Memory leak in Open vSwitch 2.17.8 allows remote attackers to interrupt service by triggering a failed packet-capture file open. ovs_pcap_open allocates its p_file structure before calling fopen but, on an fopen failure, returns without releasing that allocation. Public evidence demonstrates the leak only through a local test harness, leaving the production request path and repetition rate needed for service interruption undisclosed.
Summary
What happened
Memory leak in Open vSwitch 2.17.8 allows remote attackers to interrupt service by triggering a failed packet-capture file open. ovs_pcap_open allocates its p_file structure before calling fopen but, on an fopen failure, returns without releasing that allocation. Public evidence demonstrates the leak only through a local test harness, leaving the production request path and repetition rate needed for service interruption undisclosed.
The record
- CVE
- CVE-2024-22563
- Published
- Jan 19, 2024
- Updated
- Jun 2, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 19, 2024CVE publishedPublication date reported by the CVE source.
- Jun 2, 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.
Weakness, pattern, technique
Public exploit references
- ovs_pcap_open memory-leak proof of conceptproof of concept · demonstrated
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