🎯 CVE-2026-46050 LOW 3.1 🔥 EPSS 10% 🇪🇺 EUVD
📄 .md Alle CVEs anzeigen ✕

CVE-2026-46050 | 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

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
[] raise_barrier+0xce/0x1c0
[] raid10_sync_request+0x1ca/0x1ed0
[] md_do_sync+0x779/0x1110
[] md_thread+0x90/0x160
[] kthread+0xbe/0xf0
[] ret_from_fork+0x34/0x50
[] ret_from_fork_asm+0x1a/0x30

kworker/u1040:2+flush-253:4
[] wait_barrier+0x1de/0x220
[] regular_request_wait+0x30/0x180
[] raid10_make_request+0x261/0x1000
[] md_handle_request+0x13b/0x230
[] __submit_bio+0x107/0x1f0
[] submit_bio_noacct_nocheck+0x16f/0x390
[] ext4_io_submit+0x24/0x40
[] ext4_do_writepages+0x254/0xc80
[] ext4_writepages+0x84/0x120
[] do_writepages+0x7a/0x260
[] __writeback_single_inode+0x3d/0x300
[] writeback_sb_inodes+0x1dd/0x470
[] __writeback_inodes_wb+0x4c/0xe0
[] wb_writeback+0x18b/0x2d0
[] wb_workfn+0x2a1/0x400
[] process_one_work+0x149/0x330
[] worker_thread+0x2d2/0x410
[] kthread+0xbe/0xf0
[] ret_from_fork+0x34/0x50
[] ret_from_fork_asm+0x1a/0x30

Klassifikation & Betroffenheit:
Linux Linux 43806c3d5b9bb7d74ba4e33a6a8a41ac988bde24 <1cdff2937c618f81058422bbdc4974a3e7ec9379Linux 5.15.189 <5.15.209Linux patch: 7.0.4Linux 6.16Linux patch: 7.1Linux patch: 6.18.27Linux 9af149ca9d0dab6e59e813519d309eff62499864 <ae356d5eb1331d678985799f893e436314834a87Linux 43806c3d5b9bb7d74ba4e33a6a8a41ac988bde24 <7d96f3120a7fb7210d21b520c5b6f495da6ba436
Improper Control of Generation of Code ('Code Injection') 🎯 Medium

The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

🛡️ Empfohlene Mitigation: Refactor your program so that you do not have to dynamically generate code.
Vollständige Definition bei MITRE ➔
🩹 Patch verfügbar (OSV):
🩹 Kernel ≥ 5.15.209 🩹 Kernel ≥ 6.1.175 🩹 Kernel ≥ 6.6.140 🩹 Kernel ≥ 6.12.86 🩹 Kernel ≥ 6.18.27 🩹 Kernel ≥ 7.0.4
📚 Referenzen & Quellen:
Ausnutzungs-Zeitleiste:
Veröffentlicht:27.05.2026
Aktualisiert:17.06.2026 10:52
Assigner (CNA):Linux
EUVD-ID:EUVD-2026-32432
Quellen: 🇪🇺 EUVD-Datenbank (ENISA) + 🇺🇸 NVD-Anreicherung · 24-h-Cache
CWE-94: Code Injection ✓ Offizieller Patch / Advisory verfügbar
💡 Gegenmaßnahme: Kernel-Paket aktualisieren (apt upgrade linux-image / yum update kernel) und System neu starten.
🔴 Live Security Advisory & EPSS Exploit Radar

Zero-Day & Vulnerability Intelligence Hub

Echtzeit-Tracking mit EPSS Exploit-Wahrscheinlichkeiten, Angriffsvektor-Decodern und KI-Patch-Anleitungen.

354k+ 🇪🇺 EUVD-Datenbank
0 🔴 Critical im Radar
0 ⚠️ CISA KEV
0 🔓 Aktiv ausgenutzt
0 🧪 PoC verfügbar
📊 Historien-Charts — Criticals-Trend · Vendors · EPSS-Verteilung
🔴 Criticals pro Monat (12 M) 2025-09: 190 2025-10: 316 2025-11: 257 2025-12: 426 2026-01: 431 2026-02: 418 2026-03: 652 2026-04: 574 2026-05: 683 2026-06: 942 2026-07: 1333 2026-08: 1329 7.551 Criticals gesamt
🏢 Top-Vendor-Veröffentlichungen (6 M) Adobe Apple Google Linux Microsoft Oracle Corporation
● Adobe ● Apple ● Google ● Linux ● Microsoft ● Oracle
📈 EPSS-Verteilung (Messungen)
Tier2026-08-292026-09-06
≥90 %40
≥50 %40
≥10 %30
<10 %304300
Frühindikator · FIRST.org
Datenquellen & Methodik: Primärquelle ist die EUVD der ENISA (laufender Datenbank-Sync, alle 15 Minuten), abgeglichen mit dem CISA-KEV-Katalog und der NVD — Detail-Dossiers reichern fehlende Felder live per NVD an — mit Fallback auf CIRCL vulnerability-lookup (EU/Non-Profit, aggregiert CVE-, GitHub- und OSV-Advisories). Der CISA-KEV-Katalog (Known Exploited Vulnerabilities, ~1.700 aktiv ausgenutzte Schwachstellen) wird bei jedem Sync vollständig neu geladen und kreuzreferenziert — filterbar über die KEV-Pille. CVSS 3.1 wird nach Ampel-Logik aus Verteidigersicht dekodiert; EPSS bezeichnet die 30-Tage-Exploit-Wahrscheinlichkeit (FIRST.org).
🇪🇺 ENISA EUVD 🇺🇸 NVD ⚠️ CISA KEV ⚡ EPSS
Ökosystem & Hersteller Bedrohungs-Matrix:
Linux 1
Schweregrad & Status:
Hersteller (Datenbank-weit, 90.597 Einträge):
Quelle:
Schwachstellen-Kategorie (CWE):
🔍
3.1 LOW
🇪🇺 EUVD
EPSS 10%
CVE-2026-46050 💻 Lokal 🔓 Keine Authentifizierung nötig
Linux

CVE-2026-46050 | 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

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 block

CWE-94: Code Injection ✓ Offizieller Patch / Advisory verfügbar
💡 Gegenmaßnahme: Kernel-Paket aktualisieren (apt upgrade linux-image / yum update kernel) und System neu starten.