LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38273: net: tipc: fix refcount warning in tipc_aead_encrypt

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

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A timing flaw in Linux TIPC encryption can access a network namespace after its destruction begins. The report shows a kernel reference-count/use-after-free warning during cleanup, not a demonstrated attack. Given the 7.8 CVSS score and potential high impact, affected systems warrant timely kernel updates.

Executive priority

Treat this as a high-priority, targeted kernel update rather than an internet-wide emergency. Accelerate remediation where TIPC and namespace teardown are present. Broader urgency is moderated by the local-access requirement and absence of documented active exploitation.

Technical view

A TIPC discovery timer can invoke tipc_aead_encrypt during network-namespace teardown. The added get_net() may increment an already-zero namespace reference count. The stable fix uses maybe_get_net(); if teardown has begun, it releases the bearer reference and returns -ENODEV.

Likely exposure

Exposure is most plausible on Linux systems using TIPC where network namespaces are created or destroyed. The CVSS vector requires local, low-privileged access and no user interaction. The bundle's flattened affected-version lists are ambiguous, so confirm exposure through distribution guidance and fix lineage.

Exploitation context

CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public weaponized exploit. The issue was found by syzbot as a reference-count warning. Potential confidentiality, integrity, and availability effects are rated high, but demonstrated security impact is not described.

Researcher notes

The reported regression follows a get_net() addition intended to address an earlier slab use-after-free. The replacement prevents acquiring a namespace whose reference count reached zero. Exact vulnerable and fixed ranges cannot be reliably reconstructed from the bundle's flattened version entries; inspect stable commits and vendor backports.

Mitigation direction

  • Apply a vendor-supported kernel update incorporating the applicable Linux stable fix.
  • Consult the operating-system vendor advisory for backport status and exact affected package versions.
  • Prioritize systems using TIPC and frequently creating or destroying network namespaces.

Validation and detection

  • Record the running kernel version and compare it with vendor advisories and stable-fix lineage.
  • Determine whether TIPC is available, configured, or used on each potentially affected host.
  • After updating, confirm the fixed kernel is running, not merely installed.
  • Review kernel logs for TIPC reference-count warnings during network-namespace teardown.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

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-38273 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
3Timeline events
1ADP providers
10Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-38273Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd42ed4de6aba232d946d20653a70f79158a6535b, f5c2c4eaaa5a8e7e0685ec031d480e588e263e59, b8fcae6d2e93c54cacb8f579a77d827c1c643eb5, b19fc1d0be3c3397e5968fe2627f22e7f84673b1, 689a205cd968a1572ab561b0c4c2d50a10e9d3b0, e279024617134c94fd3e37470156534d5f2b3472, e279024617134c94fd3e37470156534d5f2b3472, 4a0fddc2c0d5c28aec8c262ad4603be0bef1938c, 5.10.238, 5.15.185, 6.1.141, 6.6.93, 6.12.31, 6.14.9unaffected
LinuxLinux6.15, 0, 5.10.239, 5.15.186, 6.1.142, 6.6.94, 6.12.34, 6.15.3, 6.16affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.