CVE-2022-50715

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

N/A
Published: December 24, 2025 at 12:22 PM UTC
Updated: June 17, 2026 at 05:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.3%

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().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 4.4.195v ≥ 5.2.19v ≥ 5.3.44.14.147 ≤ v < 4.14.3034.19.77 ≤ v < 4.19.2704.4.195 ≤ v < 4.54.9.195 ≤ v < 4.9.3375.2.19 ≤ v < 5.35.3.4 ≤ v < 5.45.4 ≤ v < 5.10.1635.4 ≤ v < 5.15.865.4 ≤ v < 5.4.2295.4 ≤ v < 6.0.165.4 ≤ v < 6.1.25.4 ≤ v < 6.218a00f37f418838fbe2036f425a1ea04f93c473c4.14.1474.19.774.4.1954.9.195440c3706f1d1835d24ba5b4bbe6515e0a97e886c5.2.195.3.45.45bad5054ecd83c866502f0370edfc9aa55dc9aa77f1a6850c5d5a65c917c3165692b5179ac4cb6bb8c11e01be7f7fcbda697e8cf9aa1f4ec65816f6d6092a9624ce32491e298f6b248b6ab31b2bbc5af1db75622996af402deea9c018deb8e869ce7548
Vendor states this is fixed in 0c7c7468c3ae222e297b7dc74d6ccb69c4d0183c (fixed)
Vendor states this is fixed in 10d713532ffc67b13df61ed9c138a8ce0a186236 (fixed)
Vendor states this is fixed in 110f14a7b2eb5b8aa9df5af2d629524f2a07d543 (fixed)
Vendor states this is fixed in 19d5a0e17aba92b10d895e40ec782768cf00da23 (fixed)
Vendor states this is fixed in 22be44212cad8be96860346882d8e694b0b437b6 (fixed)
Vendor states this is fixed in a3cc41e05e8af340a2a759b168c29fffdb9194eb (fixed)
Vendor states this is fixed in b611ad14006e5be2170d9e8e611bf49dff288911 (fixed)
Vendor states this is fixed in d26364596db8f8b55277b2afb3952e05a4057a21 (fixed)
Vendor states this is fixed in d684ceb77311410aeaf5189d321f9f564838c49a (fixed)
Vendor states this is fixed in 4.14.303 (unaffected)
Vendor states this is fixed in 4.19.270 (unaffected)
Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.9.337 (unaffected)
Vendor states this is fixed in 5.10.163 (unaffected)
Vendor states this is fixed in 5.15.86 (unaffected)
Affected range stops below 5.3, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.4 (unaffected)
Vendor states this is fixed in 5.4.229 (unaffected)
Vendor states this is fixed in 6.0.16 (unaffected)
Vendor states this is fixed in 6.1.2 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card