CVE & CISA-KEV Catalog

CVE-2026-46050

MEDIUM
5.5
CVSS v3
NVD

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

How to fix

Remediation Available
linuxDebian
Fixed in:6.1.176-1CVE-2026-46050
Fixed in:6.12.86-1CVE-2026-46050
Fixed in:7.0.4-1CVE-2026-46050
linuxUbuntu
Fixed in:5.15.0-186.196USN-8575-1
Fixed in:6.8.0-136.136USN-8567-1
linux-awsUbuntu
Fixed in:5.15.0-1112.119USN-8575-2
Fixed in:6.8.0-1061.64USN-8595-2
linux-aws-5.15Ubuntu
Fixed in:5.15.0-1112.119~20.04.1USN-8575-2
linux-aws-6.8Ubuntu
Fixed in:6.8.0-1061.64~22.04.1USN-8595-3
linux-aws-fipsUbuntu
Fixed in:5.15.0-1112.119+fips1USN-8575-2
Fixed in:6.8.0-1061.64+fips1USN-8595-3
linux-azureUbuntu
Fixed in:5.15.0-1117.126USN-8575-3
Fixed in:6.8.0-1063.71USN-8606-1
linux-azure-5.15Ubuntu
Fixed in:5.15.0-1117.126~20.04.1USN-8620-1
linux-azure-6.8Ubuntu
Fixed in:6.8.0-1063.71~22.04.1USN-8606-1
linux-azure-fdeUbuntu
Fixed in:5.15.0-1117.126USN-8610-1
Fixed in:6.8.0-1062.69USN-8607-1
linux-azure-fde-5.15Ubuntu
Fixed in:5.15.0-1117.126~20.04.2USN-8620-1
linux-azure-fde-6.8Ubuntu
Fixed in:6.8.0-1062.69~22.04.1USN-8609-1
linux-azure-fipsUbuntu
Fixed in:5.15.0-1117.126+fips1USN-8620-2
Fixed in:6.8.0-1063.71+fips2USN-8608-1
linux-fipsUbuntu
Fixed in:5.15.0-186.196+fips1USN-8575-2
Fixed in:6.8.0-136.136+fips2USN-8574-2
linux-gcpUbuntu
Fixed in:5.15.0-1112.122USN-8575-1
Fixed in:6.8.0-1064.72USN-8567-1
linux-gcp-5.15Ubuntu
Fixed in:5.15.0-1112.122~20.04.1USN-8668-1
linux-gcp-6.8Ubuntu
Fixed in:6.8.0-1064.72~22.04.1USN-8567-1
linux-gcp-fipsUbuntu
Fixed in:5.15.0-1112.122+fips1USN-8575-1
Fixed in:6.8.0-1064.72+fips1USN-8574-1
linux-gkeUbuntu
Fixed in:5.15.0-1108.114USN-8575-1
Fixed in:6.8.0-1059.67USN-8567-1
linux-gkeopUbuntu
Fixed in:5.15.0-1095.103USN-8575-1
Fixed in:6.8.0-1046.50USN-8567-1
linux-hwe-5.15Ubuntu
Fixed in:5.15.0-186.196~20.04.1USN-8575-1
linux-hwe-6.8Ubuntu
Fixed in:6.8.0-136.136~22.04.1USN-8619-1
linux-hwe-7.0Ubuntu
Fixed in:7.0.0-28.28~24.04.1USN-8569-1
linux-ibmUbuntu
Fixed in:5.15.0-1106.110USN-8575-2
Fixed in:6.8.0-1061.62USN-8574-3
linux-ibm-5.15Ubuntu
Fixed in:5.15.0-1106.110~20.04.1USN-8597-1
linux-ibm-6.8Ubuntu
Fixed in:6.8.0-1061.62~22.04.1USN-8574-3
linux-image-5.15.0-1053-nvidia-tegra-igxUbuntu
Fixed in:5.15.0-1053.53USN-8576-2
linux-image-5.15.0-1053-nvidia-tegra-igx-rtUbuntu
Fixed in:5.15.0-1053.53USN-8576-2
linux-image-5.15.0-1064-nvidia-tegraUbuntu
Fixed in:5.15.0-1064.66~20.04.1USN-8576-1
Fixed in:5.15.0-1064.66USN-8576-2
linux-image-5.15.0-1064-nvidia-tegra-rtUbuntu
Fixed in:5.15.0-1064.66~20.04.1USN-8576-1
Fixed in:5.15.0-1064.66USN-8576-2

This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.

TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works

Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.

CVSS v3 Vector

Exploitability

Attack VectorLocal
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityNone
IntegrityNone
AvailabilityHigh

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploit Intelligence

0.10%probability of exploitation in 30 days
1stpercentile

Low risk: more likely to be exploited than 1% of all known CVEs.

References

Related Vulnerabilities

Other CWE-667 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2019-10072High7.573%-Fix
CVE-2002-1850High7.517%-Fix
CVE-2009-2699High7.514%-Fix
CVE-2004-0174High7.512%--
CVE-2009-4272High7.511%--
CVE-2020-24606High8.65.2%-Fix

Common questions

How do I fix CVE-2026-46050?

Published advisories record a fix for 256 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.

Is CVE-2026-46050 being actively exploited?

Not that we know of. CVE-2026-46050 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.10% is the estimated probability that it will be exploited in the next 30 days. That is higher than 1% of all scored CVEs.

How severe is CVE-2026-46050?

CVE-2026-46050 has a CVSS v3 base score of 5.5, rated moderate. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

What does CVE-2026-46050 affect?

Published advisories record a fix for linux (Debian), linux (Ubuntu), linux-aws (Ubuntu), linux-aws-5.15 (Ubuntu), and 252 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.

Embed a live status badge for CVE-2026-46050
CVE-2026-46050 severity badge

Markdown

[![CVE-2026-46050](https://tridentstack.com/cve/badge/CVE-2026-46050.svg)](https://tridentstack.com/cve/CVE-2026-46050)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-46050"><img src="https://tridentstack.com/cve/badge/CVE-2026-46050.svg" alt="CVE-2026-46050"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-06-16.