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

> A use-after-free in the Linux kernel networking stack can cause a system crash when using Open vSwitch with tunnels and cached destinations.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Apr 2025
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-69539, BELL-CVE-2025-22057, DEBIAN-CVE-2025-22057, GHSA-f6x4-fwp3-vv23, ROOT-OS-DEBIAN-11-CVE-2025-22057, ROOT-OS-DEBIAN-12-CVE-2025-22057, ROOT-OS-UBUNTU-2204-CVE-2025-22057, ROOT-OS-UBUNTU-2404-CVE-2025-22057, UBUNTU-CVE-2025-22057

## What is CVE-2025-22057?

CVE-2025-22057 is a high-severity use after free vulnerability in Linux kernel, published on 16 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2025-22057?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-22057?

Apply the vendor's patch.

## Is CVE-2025-22057 being exploited?

There is no known exploitation of CVE-2025-22057 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-22057 and fix it if it is affected.

What it is: CVE-2025-22057 is a high-severity use after free vulnerability in Linux kernel, published on 16 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-22057 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-22057/ (Markdown: https://insights.sbomify.com/CVE-2025-22057/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-22057
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-22057
- OSV: https://osv.dev/vulnerability/CVE-2025-22057

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-22057/
Summaries are generated and may contain mistakes; the official description above is the record.