CVE-2026-63801tipc: fix slab-use-after-free Read in tipc_aead_decrypt_done
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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 ffff8881056258a8 by task kworker/u16:2/51 Workqueue: events_unbound Call Trace: tipc_aead_decrypt_done (net/tipc/crypto.c:999) process_one_work (kernel/workqueue.c:3314) worker_thread (kernel/workqueue.c:3397 kernel/workqueue.c:3478) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245) Allocated by task 169: __kasan_kmalloc (mm/kasan/common.c:398 mm/kasan/common.c:415) tipc_crypto_start (net/tipc/crypto.c:1502) tipc_init_net (net/tipc/core.c:72) ops_init (net/core/net_namespace.c:137) setup_net (net/core/net_namespace.c:446) copy_net_ns (net/core/net_namespace.c:579) create_new_namespaces (kernel/nsproxy.c:132) __x64_sys_unshare (kernel/fork.c:3316) do_syscall_64 (arch/x86/entry/syscall_64.c:63) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121) Freed by task 8: kfree (mm/slub.c:6566) tipc_exit_net (net/tipc/core.c:119) cleanup_net (net/core/net_namespace.c:704) process_one_work (kernel/workqueue.c:3314) kthread (kernel/kthread.c:436) This is the same class of bug that commit e279024617134 ("net/tipc: fix slab-use-after-free Read in tipc_aead_encrypt_done") fixed for the encrypt side. The encrypt path takes maybe_get_net(aead->crypto->net) before crypto_aead_encrypt() and drops it with put_net() on the synchronous return paths and in tipc_aead_encrypt_done(); the -EINPROGRESS/-EBUSY return keeps the reference for the async callback to release. The decrypt path was left without the equivalent guard. Mirror the encrypt-side fix on the decrypt path: take a net reference before crypto_aead_decrypt() (failing with -ENODEV and the matching bearer put if it cannot be acquired), keep it across the -EINPROGRESS/-EBUSY async return, and drop it with put_net() on the synchronous success/error return and at the end of tipc_aead_decrypt_done(). Reproduced under KASAN on v7.1-rc7: a UDP bearer with a cluster key is flooded with crafted encrypted frames from an unknown peer (driving the cluster-key decrypt path) while the bearer's netns is repeatedly torn down. The completion must run asynchronously to outlive tipc_crypto_stop(); on x86 the stock aesni gcm(aes) now decrypts synchronously, so the async path was exercised via cryptd offload. The unguarded aead->crypto dereference in tipc_aead_decrypt_done() is the unpatched upstream path; tipc_aead_decrypt() still lacks maybe_get_net(aead->crypto->net), so the completion can outlive the free on any config where crypto_aead_decrypt() goes async. Found by 0sec automated security-research tooling (https://0sec.ai).
- CVSS
- 8.8 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Analyzed
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 before 171d31245d11bf84836fad3b394cb465a4d008ec; from fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 before 2d1f21419ec121232c916d3a3fc9b6766473a0e7; from fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 before 0a780653b2a7569a7af9be7d0b00b1251baca63a; from fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 before eaca7dae02fab70c8d223cffe03cec1b93249ce2; from fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 before dca7713fe044a2067387948557ea099056e1679e; from fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 before e18769616fd5a90ec1e12aabbba544c488284292; from fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 before 1eea5e1820a2f5164d706bd1277bc97ff31ce32d; from fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 before bda3348872a2ef0d19f2df6aa8cb5025adce2f20 | CNA record |
linux linux_kernel linux:linux_kernel | from 5.5 before 5.10.260; from 5.11 before 5.15.211; from 5.16 before 6.1.177; from 6.2 before 6.6.144; from 6.7 before 6.12.95; from 6.13 before 6.18.38; from 6.19 before 7.1.3 | NVD |
References
- https://git.kernel.org/stable/c/171d31245d11bf84836fad3b394cb465a4d008ecpatch
- https://git.kernel.org/stable/c/2d1f21419ec121232c916d3a3fc9b6766473a0e7patch
- https://git.kernel.org/stable/c/0a780653b2a7569a7af9be7d0b00b1251baca63apatch
- https://git.kernel.org/stable/c/eaca7dae02fab70c8d223cffe03cec1b93249ce2patch
- https://git.kernel.org/stable/c/dca7713fe044a2067387948557ea099056e1679epatch
- https://git.kernel.org/stable/c/e18769616fd5a90ec1e12aabbba544c488284292patch
- https://git.kernel.org/stable/c/1eea5e1820a2f5164d706bd1277bc97ff31ce32dpatch
- https://git.kernel.org/stable/c/bda3348872a2ef0d19f2df6aa8cb5025adce2f20patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.