LiveActive security incident?Get immediate response
CVE Record

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

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

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw can crash a system during poweroff after a failed RAID1 array start involving only inactive disks. The business impact is availability: affected servers using Linux software RAID1 could experience kernel errors in a narrow storage-failure scenario. No source provided indicates active exploitation.

Executive priority

Treat as a targeted reliability fix for Linux RAID1 servers, not an internet-scale emergency. Patch during normal kernel maintenance, with higher priority for storage-critical systems or environments that frequently rebuild or recover RAID arrays.

Technical view

The md/raid1 code failed to stop the mdx_raid1 thread when RAID1 array run failed. Resources could be freed while the thread remained active, leading to a NULL pointer dereference in md_check_recovery during poweroff. The fix unregisters the thread before raid1_free().

Likely exposure

Exposure is most relevant to Linux systems using md RAID1. The CVE record lists multiple Linux stable versions and commit references, but distribution-specific affected and fixed package versions require vendor confirmation.

Exploitation context

The described trigger requires assembling a RAID1 array with only inactive disks, then reaching poweroff after the failed run. This appears local and configuration-dependent. KEV is false, and the provided sources do not report active exploitation or a public exploit.

Researcher notes

The source evidence identifies root cause and fix direction but provides no CVSS, CWE, exploitability assessment, or distribution mapping. Affected version data in the CVE record is broad; validate against downstream backports before declaring exposure.

Mitigation direction

  • Update to a Linux kernel or vendor package containing the referenced stable fixes.
  • Check distribution advisories for backported fixes and exact package names.
  • Avoid operational procedures that assemble RAID1 arrays from inactive disks only until patched.
  • Prioritize systems using md RAID1 in production storage paths.

Validation and detection

  • Inventory Linux hosts using md RAID1.
  • Compare running kernel builds against vendor fixed versions or referenced kernel commits.
  • Review kernel logs for md0_raid1, md_check_recovery, or NULL pointer dereference during shutdown.
  • Confirm the fix is present through vendor changelogs or kernel source history.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50715 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
10Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5bad5054ecd83c866502f0370edfc9aa55dc9aa7, 440c3706f1d1835d24ba5b4bbe6515e0a97e886c, f1db75622996af402deea9c018deb8e869ce7548, 07f1a6850c5d5a65c917c3165692b5179ac4cb6b, 07f1a6850c5d5a65c917c3165692b5179ac4cb6b, 07f1a6850c5d5a65c917c3165692b5179ac4cb6b, 07f1a6850c5d5a65c917c3165692b5179ac4cb6b, 07f1a6850c5d5a65c917c3165692b5179ac4cb6b, 07f1a6850c5d5a65c917c3165692b5179ac4cb6b, b8c11e01be7f7fcbda697e8cf9aa1f4ec65816f6, 18a00f37f418838fbe2036f425a1ea04f93c473c, d6092a9624ce32491e298f6b248b6ab31b2bbc5aunaffected
LinuxLinux5.4, 0, 4.9.337, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2, 6.2affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.