Loading vulnerability…
CVE-2024-27815 is an out-of-bounds write vulnerability in Apple platforms that affects iOS, iPadOS, macOS, tvOS, visionOS, and watchOS prior to the patched releases. The flaw was addressed through improved input validation. Successful exploitation may allow a local application to trigger memory corruption and execute arbitrary code in the kernel context, resulting in kernel-privileged code execution.
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.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.
This two-file repository contains a standalone C proof-of-concept for CVE-2024-27815 and a README documenting affected XNU and Apple OS releases, build instructions, impact, and a source hash. The sole code file creates a PF_LOCAL/SOCK_DGRAM socket pair, binds one descriptor using a deliberately oversized 255-byte UNIX socket address, and writes a short datagram to reach the vulnerable XNU send path. Its crafted address overflows the 224-byte mbuf data region by 31 bytes, overwriting nearly all of an adjacent mbuf m_hdr with attacker-selected values. The stated and implemented outcome is an unprivileged local kernel panic/denial of service on vulnerable CONFIG_MBUF_MCACHE kernels. It performs no network communication and includes no remote exploitation, persistence, credential access, or command-execution capability.
This repository contains a proof-of-concept exploit for CVE-2024-27815, a buffer overflow vulnerability in the XNU kernel (Apple's macOS kernel) introduced in xnu-10002.1.13 and fixed in xnu-10063.121.3. The exploit is implemented in a single C file (TURPENTINE.c) and demonstrates how to trigger a buffer overflow in the kernel's mbuf handling by manipulating a UNIX domain socket and crafting a specific sockaddr_un structure. The exploit allows the attacker to control the m_hdr structure of a subsequent mbuf allocation, which could be a primitive for further kernel exploitation. The exploit must be run locally on a vulnerable system and does not provide a shell or direct privilege escalation, but serves as a demonstration of the vulnerability. The only fingerprintable endpoint is the UNIX domain socket file '/tmp/TURPENTINESOCKET' used during the exploit's execution. The repository also includes a README.md with compilation and usage instructions, as well as references to a writeup and hash verification.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.