linux-cve-announce - CVE-2022-50715: md/raid1: stop mdx_raid1 thread when raid1 array run failed

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: <2025122415-CVE-2022-50715-5640@gregkh>
Date: Wed, 24 Dec 2025 13:26:14 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50715: md/raid1: stop mdx_raid1 thread when raid1 array run failed

From: Greg Kroah-Hartman <gregkh@...nel.org>

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

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

md/raid1: stop mdx_raid1 thread when raid1 array run failed

fail run raid1 array when we assemble array with the inactive disk only,
but the mdx_raid1 thread were not stop, Even if the associated resources
have been released. it will caused a NULL dereference when we do poweroff.

This causes the following Oops:
    [  287.587787] BUG: kernel NULL pointer dereference, address: 0000000000000070
    [  287.594762] #PF: supervisor read access in kernel mode
    [  287.599912] #PF: error_code(0x0000) - not-present page
    [  287.605061] PGD 0 P4D 0
    [  287.607612] Oops: 0000 [#1] SMP NOPTI
    [  287.611287] CPU: 3 PID: 5265 Comm: md0_raid1 Tainted: G     U            5.10.146 #0
    [  287.619029] Hardware name: xxxxxxx/To be filled by O.E.M, BIOS 5.19 06/16/2022
    [  287.626775] RIP: 0010:md_check_recovery+0x57/0x500 [md_mod]
    [  287.632357] Code: fe 01 00 00 48 83 bb 10 03 00 00 00 74 08 48 89 ......
    [  287.651118] RSP: 0018:ffffc90000433d78 EFLAGS: 00010202
    [  287.656347] RAX: 0000000000000000 RBX: ffff888105986800 RCX: 0000000000000000
    [  287.663491] RDX: ffffc90000433bb0 RSI: 00000000ffffefff RDI: ffff888105986800
    [  287.670634] RBP: ffffc90000433da0 R08: 0000000000000000 R09: c0000000ffffefff
    [  287.677771] R10: 0000000000000001 R11: ffffc90000433ba8 R12: ffff888105986800
    [  287.684907] R13: 0000000000000000 R14: fffffffffffffe00 R15: ffff888100b6b500
    [  287.692052] FS:  0000000000000000(0000) GS:ffff888277f80000(0000) knlGS:0000000000000000
    [  287.700149] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [  287.705897] CR2: 0000000000000070 CR3: 000000000320a000 CR4: 0000000000350ee0
    [  287.713033] Call Trace:
    [  287.715498]  raid1d+0x6c/0xbbb [raid1]
    [  287.719256]  ? __schedule+0x1ff/0x760
    [  287.722930]  ? schedule+0x3b/0xb0
    [  287.726260]  ? schedule_timeout+0x1ed/0x290
    [  287.730456]  ? __switch_to+0x11f/0x400
    [  287.734219]  md_thread+0xe9/0x140 [md_mod]
    [  287.738328]  ? md_thread+0xe9/0x140 [md_mod]
    [  287.742601]  ? wait_woken+0x80/0x80
    [  287.746097]  ? md_register_thread+0xe0/0xe0 [md_mod]
    [  287.751064]  kthread+0x11a/0x140
    [  287.754300]  ? kthread_park+0x90/0x90
    [  287.757974]  ret_from_fork+0x1f/0x30

In fact, when raid1 array run fail, we need to do
md_unregister_thread() before raid1_free().

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


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

	Fixed in 4.9.337 with commit d684ceb77311410aeaf5189d321f9f564838c49a
	Fixed in 4.14.303 with commit 110f14a7b2eb5b8aa9df5af2d629524f2a07d543
	Fixed in 4.19.270 with commit 0c7c7468c3ae222e297b7dc74d6ccb69c4d0183c
	Fixed in 5.4.229 with commit 19d5a0e17aba92b10d895e40ec782768cf00da23
	Fixed in 5.10.163 with commit 10d713532ffc67b13df61ed9c138a8ce0a186236
	Fixed in 5.15.86 with commit a3cc41e05e8af340a2a759b168c29fffdb9194eb
	Fixed in 6.0.16 with commit 22be44212cad8be96860346882d8e694b0b437b6
	Fixed in 6.1.2 with commit d26364596db8f8b55277b2afb3952e05a4057a21
	Fixed in 6.2 with commit b611ad14006e5be2170d9e8e611bf49dff288911

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-50715
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/md/raid1.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/d684ceb77311410aeaf5189d321f9f564838c49a
	https://git.kernel.org/stable/c/110f14a7b2eb5b8aa9df5af2d629524f2a07d543
	https://git.kernel.org/stable/c/0c7c7468c3ae222e297b7dc74d6ccb69c4d0183c
	https://git.kernel.org/stable/c/19d5a0e17aba92b10d895e40ec782768cf00da23
	https://git.kernel.org/stable/c/10d713532ffc67b13df61ed9c138a8ce0a186236
	https://git.kernel.org/stable/c/a3cc41e05e8af340a2a759b168c29fffdb9194eb
	https://git.kernel.org/stable/c/22be44212cad8be96860346882d8e694b0b437b6
	https://git.kernel.org/stable/c/d26364596db8f8b55277b2afb3952e05a4057a21
	https://git.kernel.org/stable/c/b611ad14006e5be2170d9e8e611bf49dff288911