[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025050133-CVE-2022-49822-1913@gregkh>
Date: Thu, 1 May 2025 16:10:12 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-49822: cifs: Fix connections leak when tlink setup failed
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
cifs: Fix connections leak when tlink setup failed
If the tlink setup failed, lost to put the connections, then
the module refcnt leak since the cifsd kthread not exit.
Also leak the fscache info, and for next mount with fsc, it will
print the follow errors:
CIFS: Cache volume key already in use (cifs,127.0.0.1:445,TEST)
Let's check the result of tlink setup, and do some cleanup.
The Linux kernel CVE team has assigned CVE-2022-49822 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.0 with commit 56c762eb9bee330bb4e6d11c589434f2904d3ab6 and fixed in 5.15.81 with commit a9059e338fc000c0b87d8cf29e93c74fd703212e
Issue introduced in 5.0 with commit 56c762eb9bee330bb4e6d11c589434f2904d3ab6 and fixed in 6.0.10 with commit 0a087842d10b5daa123ee5291e386cdd78413705
Issue introduced in 5.0 with commit 56c762eb9bee330bb4e6d11c589434f2904d3ab6 and fixed in 6.1 with commit 1dcdf5f5b2137185cbdd5385f29949ab3da4f00c
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-2022-49822
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/cifs/connect.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/a9059e338fc000c0b87d8cf29e93c74fd703212e
https://git.kernel.org/stable/c/0a087842d10b5daa123ee5291e386cdd78413705
https://git.kernel.org/stable/c/1dcdf5f5b2137185cbdd5385f29949ab3da4f00c
Powered by blists - more mailing lists