linux-cve-announce - CVE-2022-49541: cifs: fix potential double free during failed mount

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 for Android: free password hash cracker in your pocket

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

Message-ID: <2025022614-CVE-2022-49541-7460@gregkh>
Date: Wed, 26 Feb 2025 03:13:35 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2022-49541: cifs: fix potential double free during failed mount

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

cifs: fix potential double free during failed mount

RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=2088799

The Linux kernel CVE team has assigned CVE-2022-49541 to this issue.


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

	Fixed in 5.15.46 with commit ce0008a0e410cdd95f0d8cd81b2902ec10a660c4
	Fixed in 5.17.14 with commit 9a167fc440e5693c1cdd7f07071e05658bd9d89d
	Fixed in 5.18.3 with commit ee71f8f1cd3c8c4a251fd3e8abc89215ae3457cb
	Fixed in 5.19 with commit 8378a51e3f8140f60901fb27208cc7a6e47047b5

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-49541
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/cifsfs.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/ce0008a0e410cdd95f0d8cd81b2902ec10a660c4
	https://git.kernel.org/stable/c/9a167fc440e5693c1cdd7f07071e05658bd9d89d
	https://git.kernel.org/stable/c/ee71f8f1cd3c8c4a251fd3e8abc89215ae3457cb
	https://git.kernel.org/stable/c/8378a51e3f8140f60901fb27208cc7a6e47047b5