CVE-2025-38052: net/tipc: fix slab-use-after-free Read in tipc_aead_encrypt_done
In the Linux kernel, the following vulnerability has been resolved:
net/tipc: fix slab-use-after-free Read in tipc_aead_encrypt_done
Syzbot reported a slab-use-after-free with the following call trace:
==================================================================
BUG: KASAN: slab-use-after-free in tipc_aead_encrypt_done+0x4bd/0x510 net/tipc/crypto.c:840
Read of size 8 at addr ffff88807a733000 by task kworker/1:0/25
Call Trace:
kasan_report+0xd9/0x110 mm/kasan/report.c:601
tipc_aead_encrypt_done+0x4bd/0x510 net/tipc/crypto.c:840
crypto_request_complete include/crypto/algapi.h:266
aead_request_complete include/crypto/internal/aead.h:85
cryptd_aead_crypt+0x3b8/0x750 crypto/cryptd.c:772
crypto_request_complete include/crypto/algapi.h:266
cryptd_queue_worker+0x131/0x200 crypto/cryptd.c:181
process_one_work+0x9fb/0x1b60 kernel/workqueue.c:3231
Allocated by task 8355:
kzalloc_noprof include/linux/slab.h:778
tipc_crypto_start+0xcc/0x9e0 net/tipc/crypto.c:1466
tipc_init_net+0x2dd/0x430 net/tipc/core.c:72
ops_init+0xb9/0x650 net/core/net_namespace.c:139
setup_net+0x435/0xb40 net/core/net_namespace.c:343
copy_net_ns+0x2f0/0x670 net/core/net_namespace.c:508
create_new_namespaces+0x3ea/0xb10 kernel/nsproxy.c:110
unshare_nsproxy_namespaces+0xc0/0x1f0 kernel/nsproxy.c:228
ksys_unshare+0x419/0x970 kernel/fork.c:3323
__do_sys_unshare kernel/fork.c:3394
Freed by task 63:
kfree+0x12a/0x3b0 mm/slub.c:4557
tipc_crypto_stop+0x23c/0x500 net/tipc/crypto.c:1539
tipc_exit_net+0x8c/0x110 net/tipc/core.c:119
ops_exit_list+0xb0/0x180 net/core/net_namespace.c:173
cleanup_net+0x5b7/0xbf0 net/core/net_namespace.c:640
process_one_work+0x9fb/0x1b60 kernel/workqueue.c:3231
After freed the tipc_crypto tx by delete namespace, tipc_aead_encrypt_done
may still visit it in cryptd_queue_worker workqueue.
I reproduce this issue by:
ip netns add ns1
ip link add veth1 type veth peer name veth2
ip link set veth1 netns ns1
ip netns exec ns1 tipc bearer enable media eth dev veth1
ip netns exec ns1 tipc node set key this_is_a_master_key master
ip netns exec ns1 tipc bearer disable media eth dev veth1
ip netns del ns1
The key of reproduction is that, simd_aead_encrypt is interrupted, leading
to crypto_simd_usable() return false. Thus, the cryptd_queue_worker is
triggered, and the tipc_crypto tx will be visited.
tipc_disc_timeout
tipc_bearer_xmit_skb
tipc_crypto_xmit
tipc_aead_encrypt
crypto_aead_encrypt
// encrypt()
simd_aead_encrypt
// crypto_simd_usable() is false
child = &ctx->cryptd_tfm->base;
simd_aead_encrypt
crypto_aead_encrypt
// encrypt()
cryptd_aead_encrypt_enqueue
cryptd_aead_enqueue
cryptd_enqueue_request
// trigger cryptd_queue_worker
queue_work_on(smp_processor_id(), cryptd_wq, &cpu_queue->work)
Fix this by holding net reference count before encrypt.
CVE-2025-38052 is a Linux kernel memory-safety flaw in TIPC encryption cleanup. A background crypto worker can read freed TIPC crypto state after a network namespace is deleted. The public record shows a kernel fix, but no CVSS score, no CISA KEV listing, and no cited active exploitation.
Executive priority
Treat as a kernel maintenance item with elevated attention for container hosts, lab systems, or services using TIPC. There is not enough sourced evidence to classify it as an emergency, but kernel memory-safety fixes should not wait indefinitely.
Technical view
The flaw is a slab-use-after-free read in net/tipc/crypto.c, specifically tipc_aead_encrypt_done. The source describes a race where TIPC crypto transmit state is freed during namespace teardown while cryptd_queue_worker can still access it. The kernel fix holds a net reference before encryption.
Likely exposure
Exposure is most relevant to Linux systems using TIPC with encryption and network namespace operations. The source reproduction uses TIPC bearer setup, a master key, bearer disablement, and namespace deletion. Systems not loading or using TIPC are less likely to be exposed, but confirm kernel configuration and runtime module state.
Exploitation context
The issue was reported by syzbot and reproduced in a controlled kernel testing scenario. The bundle does not cite public weaponization, in-the-wild exploitation, or KEV inclusion. Exploitability beyond the reported use-after-free read is not established by the provided sources.
Researcher notes
The key condition is lifetime mismatch between TIPC crypto transmit state and asynchronous cryptd completion after namespace teardown. The source states the fix is to hold a net reference before encrypt. Avoid assuming privilege escalation, remote reachability, or crash reliability from the provided evidence alone.
Mitigation direction
Apply vendor kernel updates containing the listed stable fixes.
Prioritize hosts using TIPC, network namespaces, or container-style namespace creation.
If TIPC is unnecessary, review vendor guidance for disabling or preventing module load.
Track Debian LTS advisories if using Debian-packaged kernels.
Do not deploy directly from unverified patches; use trusted kernel packages.
Validation and detection
Inventory Linux kernel versions and compare against vendor-fixed releases.
Check whether TIPC support is built in, loaded, or operationally used.
Identify workloads allowed to create or destroy network namespaces.
Confirm installed kernels include the relevant stable commit for their branch.
Review kernel logs for TIPC, KASAN, or crash evidence if testing kernels are used.
Based on public source material and reviewed before publication.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38052 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
1ADP providers
10Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jun 18, 2025, 09:33 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.