Loading vulnerability…
CVE-2024-27395 is a use-after-free vulnerability in the Linux kernel Open vSwitch connection-tracking cleanup path, ovs_ct_exit. During traversal of connection-tracking limit entries, the cleanup code used an RCU list traversal while scheduling entries for deferred freeing with kfree_rcu. Because the deferred free operation was not protected by the traversal's RCU read-side critical section, an RCU grace period could complete during iteration and free an entry that the traversal could still access. The upstream fix replaces the traversal with a safe hash-list iteration mechanism suitable for removal and deferred freeing.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Use-after-free vulnerability in the Linux kernel Open vSwitch connection-tracking teardown path, ovs_ct_exit().
Linux kernel Open vSwitch use-after-free vulnerability in ovs_ct_exit.
Linux kernel Open vSwitch use-after-free flaw fixed in the updated image.
Linux kernel Open vSwitch connection-tracking exit use-after-free vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.