CVE-2022-50715: md/raid1: stop mdx_raid1 thread when raid1 array run failed
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.28% (FIRST EPSS).
- Fixed version: Linux Linux 0c7c7468c3ae222e297b7dc74d6ccb69c4d0183c, 10d713532ffc67b13df61ed9c138a8ce0a186236, 110f14a7b2eb5b8aa9df5af2d629524f2a07d543.
Low priority for now. Upgrade to Linux Linux 0c7c7468c3ae222e297b7dc74d6ccb69c4d0183c, 10d713532ffc67b13df61ed9c138a8ce0a186236, 110f14a7b2eb5b8aa9df5af2d629524f2a07d543 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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().
- Published
- Dec 24, 2025
- Updated
- Nov 10, 2026
- EPSS
- 0.2% · 21th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- b8c11e01be7f7fcbda697e8cf9aa1f4ec65816f6, 18a00f37f418838fbe2036f425a1ea04f93c473c, d6092a9624ce32491e298f6b248b6ab31b2bbc5a, 5.4affected
- 5bad5054ecd83c866502f0370edfc9aa55dc9aa7 and later · before d684ceb77311410aeaf5189d321f9f564838c49aaffected · git
- 440c3706f1d1835d24ba5b4bbe6515e0a97e886c and later · before 110f14a7b2eb5b8aa9df5af2d629524f2a07d543affected · git
- f1db75622996af402deea9c018deb8e869ce7548 and later · before 0c7c7468c3ae222e297b7dc74d6ccb69c4d0183caffected · git
- 07f1a6850c5d5a65c917c3165692b5179ac4cb6b and later · before 19d5a0e17aba92b10d895e40ec782768cf00da23affected · git
- 07f1a6850c5d5a65c917c3165692b5179ac4cb6b and later · before 10d713532ffc67b13df61ed9c138a8ce0a186236affected · git
- 07f1a6850c5d5a65c917c3165692b5179ac4cb6b and later · before a3cc41e05e8af340a2a759b168c29fffdb9194ebaffected · git
- 07f1a6850c5d5a65c917c3165692b5179ac4cb6b and later · before 22be44212cad8be96860346882d8e694b0b437b6affected · git
- 07f1a6850c5d5a65c917c3165692b5179ac4cb6b and later · before d26364596db8f8b55277b2afb3952e05a4057a21affected · git
- 07f1a6850c5d5a65c917c3165692b5179ac4cb6b and later · before b611ad14006e5be2170d9e8e611bf49dff288911affected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.4-1 | 6.1.4-1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kernel-default | before 4.12.14-122.290.1 | 4.12.14-122.290.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_76 | before 1-8.7.1 | 1-8.7.1 |
| SUSE:Linux Enterprise Server 12 SP5-LTSS | kernel-source | before 4.12.14-122.290.1 | 4.12.14-122.290.1 |
| SUSE:Linux Enterprise Server 12 SP5-LTSS | kernel-syms | before 4.12.14-122.290.1 | 4.12.14-122.290.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2022-50713Dec 24, 2025 · clk: visconti: Fix memory leak in visconti_register_pll()0Monitor
- ← EarlierCVE-2022-50714Dec 24, 2025 · wifi: mt76: mt7921e: fix rmmod crash in driver reload test0Monitor
- Later →CVE-2022-50716Dec 24, 2025 · wifi: ar5523: Fix use-after-free on ar5523_cmd() timed out0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0c7c7468c3ae222e297b7dc74d6ccb69c4d0183c | Vendor (CNA) |
| Linux Linux | 10d713532ffc67b13df61ed9c138a8ce0a186236 | Vendor (CNA) |
| Linux Linux | 110f14a7b2eb5b8aa9df5af2d629524f2a07d543 | Vendor (CNA) |
| Linux Linux | 19d5a0e17aba92b10d895e40ec782768cf00da23 | Vendor (CNA) |
| Linux Linux | 22be44212cad8be96860346882d8e694b0b437b6 | Vendor (CNA) |
| Linux Linux | 4.14.303 | Vendor (CNA) |
| Linux Linux | 4.19.270 | Vendor (CNA) |
| Linux Linux | 4.5 | Vendor (CNA) |
| Linux Linux | 4.9.337 | Vendor (CNA) |
| Linux Linux | 5.3 | Vendor (CNA) |
| Linux Linux | 5.4 | Vendor (CNA) |
| Linux Linux | a3cc41e05e8af340a2a759b168c29fffdb9194eb | Vendor (CNA) |
| Linux Linux | b611ad14006e5be2170d9e8e611bf49dff288911 | Vendor (CNA) |
| Linux Linux | d26364596db8f8b55277b2afb3952e05a4057a21 | Vendor (CNA) |
| Linux Linux | d684ceb77311410aeaf5189d321f9f564838c49a | Vendor (CNA) |
| debian:linux | 6.1.4-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-default | 4.12.14-122.290.1 · SUSE:Linux Enterprise Live Patching 12 SP5 | Package registry (OSV) |
| suse:kernel-source | 4.12.14-122.290.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
| suse:kernel-syms | 4.12.14-122.290.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
| suse:kgraft-patch-SLE12-SP5_Update_76 | 1-8.7.1 · SUSE:Linux Enterprise Live Patching 12 SP5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/10d713532ffc67b13df61ed9c138a8ce0a186236
- git.kernel.org/stable/c/110f14a7b2eb5b8aa9df5af2d629524f2a07d543
- git.kernel.org/stable/c/19d5a0e17aba92b10d895e40ec782768cf00da23
- git.kernel.org/stable/c/22be44212cad8be96860346882d8e694b0b437b6
- git.kernel.org/stable/c/a3cc41e05e8af340a2a759b168c29fffdb9194eb
- git.kernel.org/stable/c/b611ad14006e5be2170d9e8e611bf49dff288911
- git.kernel.org/stable/c/d26364596db8f8b55277b2afb3952e05a4057a21
- git.kernel.org/stable/c/d684ceb77311410aeaf5189d321f9f564838c49a
Vendor advisories and official records. Exploit/PoC links are deliberately left out.