[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091640-CVE-2022-50351-ac59@gregkh>
Date: Tue, 16 Sep 2025 18:11:47 +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-50351: cifs: Fix xid leak in cifs_create()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
cifs: Fix xid leak in cifs_create()
If the cifs already shutdown, we should free the xid before return,
otherwise, the xid will be leaked.
The Linux kernel CVE team has assigned CVE-2022-50351 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.13 with commit 087f757b0129850c99cc9116df4909dac1bce871 and fixed in 5.15.76 with commit 593d877c39aa9f3fe1a4b5b022492886d7d700ec
Issue introduced in 5.13 with commit 087f757b0129850c99cc9116df4909dac1bce871 and fixed in 6.0.6 with commit 92aa09c86ef297976a3c27c6574c0839418dc2c4
Issue introduced in 5.13 with commit 087f757b0129850c99cc9116df4909dac1bce871 and fixed in 6.1 with commit fee0fb1f15054bb6a0ede452acb42da5bef4d587
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-50351
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/dir.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/593d877c39aa9f3fe1a4b5b022492886d7d700ec
https://git.kernel.org/stable/c/92aa09c86ef297976a3c27c6574c0839418dc2c4
https://git.kernel.org/stable/c/fee0fb1f15054bb6a0ede452acb42da5bef4d587
Powered by blists - more mailing lists