linux-cve-announce - CVE-2022-49178: memstick/mspro_block: fix handling of read-only devices

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: <2025022614-CVE-2022-49178-b663@gregkh>
Date: Wed, 26 Feb 2025 02:56:23 +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-49178: memstick/mspro_block: fix handling of read-only devices

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

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

memstick/mspro_block: fix handling of read-only devices

Use set_disk_ro to propagate the read-only state to the block layer
instead of checking for it in ->open and leaking a reference in case
of a read-only device.

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


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

	Fixed in 5.16.19 with commit 057b53c4f87690d626203acef8b63d52a9bf2f43
	Fixed in 5.17.2 with commit 6a0725b9d78ff6efdc95a37e4f05072e79c63918
	Fixed in 5.18 with commit 6dab421bfe06a59bf8f212a72e34673e8acf2018

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-49178
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:
	drivers/memstick/core/mspro_block.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/057b53c4f87690d626203acef8b63d52a9bf2f43
	https://git.kernel.org/stable/c/6a0725b9d78ff6efdc95a37e4f05072e79c63918
	https://git.kernel.org/stable/c/6dab421bfe06a59bf8f212a72e34673e8acf2018