LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22057: net: decrease cached dst counters in dst_release

In the Linux kernel, the following vulnerability has been resolved: net: decrease cached dst counters in dst_release Upstream fix ac888d58869b ("net: do not delay dst_entries_add() in dst_release()") moved decrementing the dst count from dst_destroy to dst_release to avoid accessing already freed data in case of netns dismantle. However in case CONFIG_DST_CACHE is enabled and OvS+tunnels are used, this fix is incomplete as the same issue will be seen for cached dsts: Unable to handle kernel paging request at virtual address ffff5aabf6b5c000 Call trace: percpu_counter_add_batch+0x3c/0x160 (P) dst_release+0xec/0x108 dst_cache_destroy+0x68/0xd8 dst_destroy+0x13c/0x168 dst_destroy_rcu+0x1c/0xb0 rcu_do_batch+0x18c/0x7d0 rcu_core+0x174/0x378 rcu_core_si+0x18/0x30 Fix this by invalidating the cache, and thus decrementing cached dst counters, in dst_release too.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux kernel networking flaw can cause a serious kernel memory fault when cached network routes are released. Exposure depends on a specific configuration: CONFIG_DST_CACHE with Open vSwitch and tunnels. A successful trigger could compromise confidentiality, integrity, and availability according to the supplied CVSS assessment, but the sources provide no evidence of active exploitation.

Executive priority

Treat this as a high-priority kernel maintenance issue for virtualization, networking, and container infrastructure using Open vSwitch tunnels. Rapidly identify matching configurations, then deploy supported kernel updates through normal change controls. Systems without the required configuration appear less likely to be exposed, but the ambiguous version data warrants vendor confirmation.

Technical view

An earlier networking change moved destination-entry counter decrements into dst_release() to prevent access to freed data during network-namespace teardown. It did not fully handle cached destinations. With CONFIG_DST_CACHE and OvS tunnels, cache destruction can reach invalid memory. The stable fixes invalidate the cache during dst_release(), ensuring cached destination counters are decremented safely.

Likely exposure

Likely exposure is limited to Linux systems using kernels identified by the CVE record, compiled with CONFIG_DST_CACHE, and running Open vSwitch with tunnels. The supplied version list is ambiguous and includes commit identifiers and unusual boundaries, so confirm exposure against distribution advisories and the referenced stable commits.

Exploitation context

The CVSS 3.1 score is 7.8 with local access, low complexity, low privileges, and no user interaction. The supplied record is not in KEV and contains no evidence of exploitation in the wild. It documents a kernel paging fault, while the CVSS assessment indicates potentially high confidentiality, integrity, and availability impact.

Researcher notes

The failure involves destination-cache lifetime and accounting during release and network-namespace teardown. The documented trace passes through dst_release(), dst_cache_destroy(), and RCU destruction before faulting in percpu counter handling. Validate fixes branch-by-branch: the references contain separate stable backports, and the supplied affected-version representation is insufficient for reliable range inference.

Mitigation direction

  • Apply the appropriate Linux distribution or stable-kernel update containing the referenced fix.
  • Match the installed kernel branch against the corresponding stable commit before scheduling remediation.
  • Prioritize systems using Open vSwitch tunnels and kernels built with CONFIG_DST_CACHE.
  • If updating is delayed, consult the Linux distributor for supported mitigations or configuration guidance.

Validation and detection

  • Record installed kernel versions and compare them with distribution advisories and stable fixes.
  • Verify whether each kernel configuration enables CONFIG_DST_CACHE.
  • Identify hosts running Open vSwitch with tunnel interfaces.
  • After updating, confirm the running kernel includes the branch-appropriate fix.
  • Review kernel logs for paging faults matching the documented dst_release and dst_cache_destroy call path.
Prepared
Confidence
medium
Sources
7

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-22057 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
0ADP providers
6Source 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-22057Attack 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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd71785ffc7e7cae3fbdc4ea8a9d05b7a1c59f7b8, d71785ffc7e7cae3fbdc4ea8a9d05b7a1c59f7b8, d71785ffc7e7cae3fbdc4ea8a9d05b7a1c59f7b8, d71785ffc7e7cae3fbdc4ea8a9d05b7a1c59f7b8, d71785ffc7e7cae3fbdc4ea8a9d05b7a1c59f7b8unaffected
LinuxLinux4.6, 0, 6.6.87, 6.12.23, 6.13.11, 6.14.2, 6.15affected
Weakness

CWE details

No CWE listed

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