Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-38052: net/tipc: fix slab-use-after-free Read in tipc_aead_encrypt_done

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.57% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 4a0fddc2c0d5c28aec8c262ad4603be0bef1938c, 689a205cd968a1572ab561b0c4c2d50a10e9d3b0, b19fc1d0be3c3397e5968fe2627f22e7f84673b1.

Low priority for now. Upgrade to Linux Linux 4a0fddc2c0d5c28aec8c262ad4603be0bef1938c, 689a205cd968a1572ab561b0c4c2d50a10e9d3b0, b19fc1d0be3c3397e5968fe2627f22e7f84673b1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Jun 18, 2025
Updated
Oct 15, 2026
EPSS
0.5% · 48th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
8.8
1.0 point gap

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-38052

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.5affected
    • fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 and later · before d42ed4de6aba232d946d20653a70f79158a6535baffected · git
    • fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 and later · before f5c2c4eaaa5a8e7e0685ec031d480e588e263e59affected · git
    • fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 and later · before b8fcae6d2e93c54cacb8f579a77d827c1c643eb5affected · git
    • fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 and later · before b19fc1d0be3c3397e5968fe2627f22e7f84673b1affected · git
    • fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 and later · before 689a205cd968a1572ab561b0c4c2d50a10e9d3b0affected · git
    • fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 and later · before 4a0fddc2c0d5c28aec8c262ad4603be0bef1938caffected · git
    • fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 and later · before e279024617134c94fd3e37470156534d5f2b3472affected · git
    • before 5.5not affected · semver
    • 5.10.238 and later · up to and including 5.10.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-55.25.1.el10_06.12.0-55.25.1.el10_0
AlmaLinux:10kernel-docbefore 6.12.0-55.25.1.el10_06.12.0-55.25.1.el10_0
AlmaLinux:8bpftoolbefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.66.1.rt7.407.el8_104.18.0-553.66.1.rt7.407.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.66.1.rt7.407.el8_104.18.0-553.66.1.rt7.407.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.66.1.rt7.407.el8_104.18.0-553.66.1.rt7.407.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.66.1.rt7.407.el8_104.18.0-553.66.1.rt7.407.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.66.1.rt7.407.el8_104.18.0-553.66.1.rt7.407.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.66.1.rt7.407.el8_104.18.0-553.66.1.rt7.407.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.66.1.rt7.407.el8_104.18.0-553.66.1.rt7.407.el8_10

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-38045Jun 18, 2025 · wifi: iwlwifi: fix debug actions order
    22Monitor
  • ← EarlierCVE-2025-38047Jun 18, 2025 · x86/fred: Fix system hang during S4 resume with FRED enabled
    22Monitor
  • Later →CVE-2025-38058Jun 18, 2025 · __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux4a0fddc2c0d5c28aec8c262ad4603be0bef1938cVendor (CNA)
Linux Linux689a205cd968a1572ab561b0c4c2d50a10e9d3b0Vendor (CNA)
Linux Linuxb19fc1d0be3c3397e5968fe2627f22e7f84673b1Vendor (CNA)
Linux Linuxb8fcae6d2e93c54cacb8f579a77d827c1c643eb5Vendor (CNA)
Linux Linuxd42ed4de6aba232d946d20653a70f79158a6535bVendor (CNA)
Linux Linuxe279024617134c94fd3e37470156534d5f2b3472Vendor (CNA)
Linux Linuxf5c2c4eaaa5a8e7e0685ec031d480e588e263e59Vendor (CNA)
almalinux:kernel5.14.0-570.32.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-570.32.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-570.32.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-570.32.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-570.32.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-570.32.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-570.32.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-570.32.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-570.32.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-570.32.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-abi-stablelists6.12.0-55.25.1.el10_0 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-doc6.12.0-55.25.1.el10_0 · AlmaLinux:10Package registry (OSV)
debian:linux6.1.147-1 · Debian:12Package registry (OSV)
opensuse:dtb-aarch646.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-64kb6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default-base6.12.0-160000.6.1.160000.2.4 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-docs6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-kvmsmall6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-build6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-qa6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-rt6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-source6.12.0-160000.6.1 · openSUSE:Leap 16.0Package registry (OSV)

+27

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records