linux-cve-announce - CVE-2025-22057: net: decrease cached dst counters in dst

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025041605-CVE-2025-22057-fb12@gregkh>
Date: Wed, 16 Apr 2025 16:12:28 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2025-22057: net: decrease cached dst counters in dst_release

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.

The Linux kernel CVE team has assigned CVE-2025-22057 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 4.6 with commit d71785ffc7e7cae3fbdc4ea8a9d05b7a1c59f7b8 and fixed in 6.6.87 with commit ccc331fd5bcae131d2627d5ef099d4a1f6540aea
	Issue introduced in 4.6 with commit d71785ffc7e7cae3fbdc4ea8a9d05b7a1c59f7b8 and fixed in 6.12.23 with commit 92a5c18513117be69bc00419dd1724c1940f8fcd
	Issue introduced in 4.6 with commit d71785ffc7e7cae3fbdc4ea8a9d05b7a1c59f7b8 and fixed in 6.13.11 with commit 836415a8405c9665ae55352fc5ba865c242f5e4f
	Issue introduced in 4.6 with commit d71785ffc7e7cae3fbdc4ea8a9d05b7a1c59f7b8 and fixed in 6.14.2 with commit e833e7ad64eb2f63867f65303be49ca30ee8819e
	Issue introduced in 4.6 with commit d71785ffc7e7cae3fbdc4ea8a9d05b7a1c59f7b8 and fixed in 6.15-rc1 with commit 3a0a3ff6593d670af2451ec363ccb7b18aec0c0a

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2025-22057
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	net/core/dst.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/ccc331fd5bcae131d2627d5ef099d4a1f6540aea
	https://git.kernel.org/stable/c/92a5c18513117be69bc00419dd1724c1940f8fcd
	https://git.kernel.org/stable/c/836415a8405c9665ae55352fc5ba865c242f5e4f
	https://git.kernel.org/stable/c/e833e7ad64eb2f63867f65303be49ca30ee8819e
	https://git.kernel.org/stable/c/3a0a3ff6593d670af2451ec363ccb7b18aec0c0a