CVE-2024-0646 is an out-of-bounds memory-write vulnerability in the Linux kernel Transport Layer Security (kTLS) implementation. When the splice system call is used with a kTLS socket as the destination, the kernel can write into memory pages that should be read-only. The resulting kernel memory corruption can cause a system crash and may be exploitable for local privilege escalation.
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.
25 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.
A Linux kernel kTLS flaw that can overwrite read-only memory pages through splice operations to a kTLS socket.
Linux kernel kTLS vulnerability in which splice to a kTLS socket can overwrite read-only memory pages.
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.