CVE-2026-46050 Details
Description
In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix deadlock with check operation and nowait requests When an array check is running it will raise the barrier at which point normal requests will become blocked and increment the nr_pending value to signal there is work pending inside of wait_barrier(). NOWAIT requests do not block and so will return immediately with an error, and additionally do not increment nr_pending in wait_barrier(). Upstream change commit 43806c3d5b9b ("raid10: cleanup memleak at raid10_make_request") added a call to raid_end_bio_io() to fix a memory leak when NOWAIT requests hit this condition. raid_end_bio_io() eventually calls allow_barrier() and it will unconditionally do an atomic_dec_and_test(&conf->nr_pending) even though the corresponding increment on nr_pending didn't happen in the NOWAIT case. This can be easily seen by starting a check operation while an application is doing nowait IO on the same array. This results in a deadlocked state due to nr_pending value underflowing and so the md resync thread gets stuck waiting for nr_pending to == 0. Output of r10conf state of the array when we hit this condition: crash> struct r10conf barrier = 1, nr_pending = { counter = -41 }, nr_waiting = 15, nr_queued = 0, Example of md_sync thread stuck waiting on raise_barrier() and other requests stuck in wait_barrier(): md1_resync [<0>] raise_barrier+0xce/0x1c0 [<0>] raid10_sync_request+0x1ca/0x1ed0 [<0>] md_do_sync+0x779/0x1110 [<0>] md_thread+0x90/0x160 [<0>] kthread+0xbe/0xf0 [<0>] ret_from_fork+0x34/0x50 [<0>] ret_from_fork_asm+0x1a/0x30 kworker/u1040:2+flush-253:4 [<0>] wait_barrier+0x1de/0x220 [<0>] regular_request_wait+0x30/0x180 [<0>] raid10_make_request+0x261/0x1000 [<0>] md_handle_request+0x13b/0x230 [<0>] __submit_bio+0x107/0x1f0 [<0>] submit_bio_noacct_nocheck+0x16f/0x390 [<0>] ext4_io_submit+0x24/0x40 [<0>] ext4_do_writepages+0x254/0xc80 [<0>] ext4_writepages+0x84/0x120 [<0>] do_writepages+0x7a/0x260 [<0>] __writeback_single_inode+0x3d/0x300 [<0>] writeback_sb_inodes+0x1dd/0x470 [<0>] __writeback_inodes_wb+0x4c/0xe0 [<0>] wb_writeback+0x18b/0x2d0 [<0>] wb_workfn+0x2a1/0x400 [<0>] process_one_work+0x149/0x330 [<0>] worker_thread+0x2d2/0x410 [<0>] kthread+0xbe/0xf0 [<0>] ret_from_fork+0x34/0x50 [<0>] ret_from_fork_asm+0x1a/0x30
A deadlock vulnerability has been identified in the Linux kernel's RAID10 implementation, specifically during array check operations. When a check is in progress, it raises a barrier that blocks normal requests, increasing the 'nr_pending' count to indicate pending work. However, NOWAIT requests bypass this blockage, returning an error without updating the 'nr_pending' count. A recent upstream change aimed at addressing a memory leak with NOWAIT requests inadvertently introduced a flaw. It caused the 'nr_pending' count to underflow, creating a deadlock where the RAID synchronization thread gets stuck waiting for the count to return to zero. This issue can be reproduced by initiating a check operation while simultaneously sending NOWAIT I/O requests to the same array, leading to a deadlock state.
Users can apply the latest patches available in the Linux kernel stable tree to address this vulnerability. Instructions for downloading the patched version can be found in the Linux kernel Git repository.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/1cdff2937c618f81058422bbdc4974a3e7ec9379 | kernel.org | Patch |
| https://git.kernel.org/stable/c/2249983d971e6839b36284e6610390b2c217dfa1 | kernel.org | Patch |
| https://git.kernel.org/stable/c/42fe37c90184cd1568838b84b488934c3671c963 | kernel.org | Patch |
| https://git.kernel.org/stable/c/7d96f3120a7fb7210d21b520c5b6f495da6ba436 | kernel.org | Patch |
| https://git.kernel.org/stable/c/965d6162dd88cc7cc193cf7f5bfc132d8bbf0523 | kernel.org | Patch |
| https://git.kernel.org/stable/c/ae356d5eb1331d678985799f893e436314834a87 | kernel.org | Patch |
| https://git.kernel.org/stable/c/cac2106bb9a2180b288079b49ed626414fb5bc45 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-667 | Improper Locking | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.15.189, < 5.15.209 >= 6.1.146, < 6.1.175 >= 6.6.99, < 6.6.140 >= 6.12.39, < 6.12.86 >= 6.15.7, < 6.16 >= 6.16.1, < 6.18.27 >= 6.19, < 7.0.4 6.16 - 6.16 rc6 6.16 rc7 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 16, 2026 | Initial Analysis | [email protected] |
| Jun 1, 2026 | CVE Modified | kernel.org |
| May 27, 2026 | New CVE Received | kernel.org |