VDB

CVE-2025-38273

CVE-2025-38273 PUBLISHED CVSS 7.8 HIGH

net: tipc: fix refcount warning in tipc_aead_encrypt

Reported by linux · Published July 10, 2025

In the Linux kernel, the following vulnerability has been resolved: net: tipc: fix refcount warning in tipc_aead_encrypt syzbot reported a refcount warning [1] caused by calling get_net() on a network namespace that is being destroyed (refcount=0). This happens when a TIPC discovery timer fires during network namespace cleanup. The recently added get_net() call in commit e279024617134 ("net/tipc: fix slab-use-after-free Read in tipc_aead_encrypt_done") attempts to hold a reference to the network namespace. However, if the namespace is already being destroyed, its refcount might be zero, leading to the use-after-free warning. Replace get_net() with maybe_get_net(), which safely checks if the refcount is non-zero before incrementing it. If the namespace is being destroyed, return -ENODEV early, after releasing the bearer reference. [1]: https://lore.kernel.org/all/68342b55.a70a0220.253bc2.0091.GAE@google.com/T/#m12019cf9ae77e1954f666914640efa36d52704a2

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
linux_kernellinux6.15.3, 6.15, 6.12.34

Risk scores

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

Affected products

VendorProductVersions
LinuxLinuxd42ed4de6aba232d946d20653a70f79158a6535b, f5c2c4eaaa5a8e7e0685ec031d480e588e263e59, b8fcae6d2e93c54cacb8f579a77d827c1c643eb5
LinuxLinux6.15, 0, 5.10.239
linuxlinux_kernel5.10.238, 6.1.141, 6.6.93
LinuxLinux*, *, *

Timeline

  • Jul 9, 2025 CVE Published
  • Jul 10, 2025 EPSS Score (30 in total, the first dated here)
  • Oct 11, 2025 PoC Published (30 in total, the first dated here)
  • Apr 29, 2026 Distribution Patch (103 in total, the first dated here)
  • Apr 29, 2026 Security Advisory (109 in total, the first dated here)
  • Jun 9, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-38273
vulnetix vdb fixes CVE-2025-38273

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-38273/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›