Loading vulnerability…
CVE-2024-0646 is an out-of-bounds memory write vulnerability in the Linux kernel Kernel Transport Layer Security (kTLS) implementation. The flaw occurs when the splice function is invoked with a kTLS socket as its destination, allowing kTLS to overwrite read-only memory pages. A local low-privileged attacker may exploit the condition to corrupt kernel memory, crash the system, or potentially escalate privileges.
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.
32 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Vulnerability addressed by the AlmaLinux 9.2 TuxCare advisory.
A vulnerability included in the TuxCare AlmaLinux 9.2 kernel security update advisory.
Linux kernel TLS splice out-of-bounds write vulnerability presented as an example of a theoretically serious but operationally low-priority flaw due to local access requirements and low exploitation likelihood.
Linux kernel kTLS vulnerability allowing read-only memory pages to be overwritten when splice() targets a kTLS socket.
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.