In the Linux kernel, the following vulnerability has been resolved: tipc: fix slab-use-after-free Read in tipc_aead_decrypt_done tipc_aead_decrypt() goes straight from tipc_bearer_hold(b) to crypto_aead_decrypt(req) without taking a reference on the netns, unlike the encrypt path. When crypto_aead_decrypt() is offloaded asynchronously (e.g. the SIMD aead wrapper queuing to cryptd), the cryptd worker runs tipc_aead_decrypt_done() later. If the bearer's netns is torn down in the meantime, cleanup_net() -> tipc_exit_net() -> tipc_crypto_stop() frees the per-netns tipc_crypto, and the completion then reads it: tipc_aead_decrypt_done() dereferences aead->crypto->stats and aead->crypto->net, and tipc_crypto_rcv_complete() dereferences aead->crypto->aead[] and the node table -- reading freed memory. Decoded KASAN splat (v7.1-rc7, CONFIG_KASAN_INLINE + TIPC + TIPC_CRYPTO): BUG: KASAN: slab-use-after-free in tipc_aead_decrypt_done (net/tipc/crypto.c:999) Read of size 8 at addr ffff88810
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2026-63801 is a slab-use-after-free vulnerability in the Linux kernel's TIPC (Transparent Inter-Process Communication) protocol implementation. The flaw occurs in tipc_aead_decrypt_done() when asynchronous cryptographic operations are offloaded to workers like cryptd. Unlike the encryption path, the decryption flow fails to maintain a reference on the network namespace before initiating crypto_aead_decrypt(). If the bearer's netns is torn down while the async operation is pending, the callback executes in a freed memory context, leading to use-after-free conditions. This vulnerability affects any Linux system using TIPC with hardware-accelerated or worker-queued crypto operations, potentially allowing local attackers to trigger kernel memory corruption and denial of service.
While CVE-2026-63801 lacks direct MITRE ATT&CK mapping, Casky's extended reasoning capabilities would identify this as a resource management and privilege escalation attack pattern. Practitioners using Casky would observe detections aligned with T1053 (Scheduled Task/Job) for async kernel worker execution patterns and T1040 (Network Sniffing) contexts where TIPC message decryption occurs. The platform's 754 mapped security skills enable detection of unsafe kernel object lifecycle management, reference counting bypasses, and namespace isolation breaks—all prerequisites for exploiting this flaw. Security teams would see findings related to memory safety violations and kernel state inconsistencies that precede use-after-free exploitation attempts.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-63801. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation