[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025041611-CVE-2025-22074-2c8b@gregkh>
Date: Wed, 16 Apr 2025 16:12:45 +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-22074: ksmbd: fix r_count dec/increment mismatch
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix r_count dec/increment mismatch
r_count is only increased when there is an oplock break wait,
so r_count inc/decrement are not paired. This can cause r_count
to become negative, which can lead to a problem where the ksmbd
thread does not terminate.
The Linux kernel CVE team has assigned CVE-2025-22074 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.6.84 with commit 09aeab68033161cb54f194da93e51a11aee6144b and fixed in 6.6.87 with commit 4790bcb269e5d6d88200a67c54ae6d627332a3be
Issue introduced in 6.12.20 with commit a4261bbc33fbf99b99c80aa3a2c5097611802980 and fixed in 6.12.23 with commit 457db486203c90e10c3efc87fd45cc7000b1cd36
Issue introduced in 6.13.8 with commit f17d1c63a76b0fe8e9c78023a86507a3a6d62cfa and fixed in 6.13.11 with commit 20378cf48359f39dee0ef9b61470ebe77bd49c0d
Issue introduced in 6.14 with commit 3aa660c059240e0c795217182cf7df32909dd917 and fixed in 6.14.2 with commit c2ec33d46b4d1c8085dab5d02e00b21f4f0fb8a9
Issue introduced in 6.14 with commit 3aa660c059240e0c795217182cf7df32909dd917 and fixed in 6.15-rc1 with commit ddb7ea36ba7129c2ed107e2186591128618864e1
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-22074
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:
fs/smb/server/oplock.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/4790bcb269e5d6d88200a67c54ae6d627332a3be
https://git.kernel.org/stable/c/457db486203c90e10c3efc87fd45cc7000b1cd36
https://git.kernel.org/stable/c/20378cf48359f39dee0ef9b61470ebe77bd49c0d
https://git.kernel.org/stable/c/c2ec33d46b4d1c8085dab5d02e00b21f4f0fb8a9
https://git.kernel.org/stable/c/ddb7ea36ba7129c2ed107e2186591128618864e1
Powered by blists - more mailing lists