Kernel memory corruption in Apple operating systems
CVE-2026-20698 is a kernel vulnerability in Apple platforms that Apple states was addressed with improved memory handling. The flaw affects the Kernel component in iOS 26.4 and iPadOS 26.4, macOS Tahoe 26.4, tvOS 26.4, visionOS 26.4, and watchOS 26.4. According to Apple’s advisory text, a local app may be able to trigger unexpected system termination or corrupt kernel memory. The available information does not identify the specific vulnerable function or root cause beyond Apple’s statement that the fix involved improved memory handling.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a standalone exploit research repo for CVE-2026-20698, a heap buffer overflow in Apple XNU routing socket handling of RTA_GENMASK via PF_ROUTE. It is not part of a larger exploit framework. The code demonstrates that an unprivileged local process can open a PF_ROUTE raw socket and send crafted RTM_GET routing messages containing RTA_DST and RTA_GENMASK sockaddrs to trigger vulnerable kernel processing in rn_addmask()/routing socket code, resulting in a reliable kernel panic and device reboot on vulnerable iOS/macOS versions prior to 26.4. Repository structure: the core PoC is pf_route_crash.c, a minimal trigger program. variant_probe.c is a broader harness that tests combinations of routing address flags, multiple RTM_* message types, varying sockaddr lengths, and checks returned data for possible leaks or kernel pointer artifacts. family_probe.c focuses on crash behavior across address families and safe/unsafe sa_len ranges, including post-stress validation. single_family.c isolates one family/length pair for targeted testing. genmask_escalate.c is not a working privilege-escalation exploit; it is an exploratory fuzzing/analysis tool that varies genmask length and inspects responses for corruption or pointer disclosure. route_26_4_variants.c tests patched behavior on iOS 26.4, including alternate route operations and sysctl-based route dump paths. variant_26_4_test.m wraps similar tests in a UIKit iOS app for on-device validation from an app context. README.md and APPLE_SUBMISSION.md document the vulnerability, affected versions, crash variants, and disclosure details. Main exploit capability: reliable local denial of service against vulnerable Apple devices by causing a kernel panic through malformed PF_ROUTE messages. The repo repeatedly uses destination IP 8.8.8.8 as a benign route lookup target and crafts genmask sockaddrs with attacker-controlled family and sa_len values. The documented severe variants include AF_UNIX and AF_LINK with minimal sa_len values, plus AF_INET/AF_INET6 boundary cases. Although the documentation discusses theoretical potential for memory corruption and kernel code execution on kernels lacking bounds-safety mitigations, no weaponized RCE or privilege-escalation payload is present. Overall maturity is best classified as POC/research-grade exploit code with extensive variant analysis rather than an operational post-exploitation tool.
Affected products & vendors
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.
Recent activity
6 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
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.