CVE-2024-22563

What it actually does

The vulnerability is a memory leak in the xmalloc__ function within openvswitch, allowing repeated allocations without corresponding deallocations that can exhaust system memory over time when triggered.

Why it matters to the business

Affected network virtualization services may experience gradual resource depletion leading to instability, degraded performance, or outages in environments relying on Open vSwitch for connectivity and traffic handling.

How an attack unfolds

An attacker identifies a vulnerable Open vSwitch instance and repeatedly exercises code paths invoking xmalloc__ through crafted network packets or configuration operations, accumulating unfreed memory until denial of service occurs.

How to fix it

Upgrade affected Debian systems to the specified fixed linux package versions: 6.1.94-1 or later for Debian 12, and 6.9.7-1 or later for Debian 13. Apply vendor patches for Open vSwitch if released separately and restart affected services.

How to confirm the fix worked

Confirm installed package versions match or exceed the fixed releases listed for each Debian distribution. Monitor runtime memory consumption of ovs processes for stabilization after updates.

Typical attack path

1. Scan for exposed systems running vulnerable Open vSwitch versions
2. Send repeated network traffic or issue operations that invoke the leaky allocation function
3. Monitor for memory growth and continue until resource exhaustion disrupts service

How to detect it

Review system and application logs for out-of-memory events tied to openvswitch processes and correlate with traffic patterns that may trigger repeated allocations.

What your security team should do

• Apply the listed Debian package upgrades immediately on all affected hosts
• Enable memory usage monitoring and alerting for Open vSwitch daemons
• Restrict network access to management interfaces until patches are deployed