VulnerabilityPublished 27 May 2026Updated 6 Nov 2026

CVE-2026-46051: Linux kernel · md/raid5: fix soft lockup in retry_aligned_read()

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in a9055300e07d9d6800264d3c2560e1d0144689ca : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:34 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch

Available – fixed in a9055300e07d9d6800264d3c2560e1d0144689ca, 09880592f5a9dc73377d6eb5ac123537b5f8df49, 4166d5234fe8b6c3c7f796a6c198605356c5b355 +5

Exploitation evidence

Disclosed: evidence found.
CVE published 27 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6, < a9055300e07d9d6800264d3c2560e1d0144689ca	Fixed in a9055300e07d9d6800264d3c2560e1d0144689ca
LinuxLinux	Affected ≥ 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6, < 09880592f5a9dc73377d6eb5ac123537b5f8df49	Fixed in 09880592f5a9dc73377d6eb5ac123537b5f8df49
LinuxLinux	Affected ≥ 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6, < 4166d5234fe8b6c3c7f796a6c198605356c5b355	Fixed in 4166d5234fe8b6c3c7f796a6c198605356c5b355
LinuxLinux	Affected ≥ 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6, < 1985cb3247e87ff6b8ca4bc5f9626f4f51024507	Fixed in 1985cb3247e87ff6b8ca4bc5f9626f4f51024507
LinuxLinux	Affected ≥ 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6, < 883cc33b7af1c448663287f069ef9dfea001e90f	Fixed in 883cc33b7af1c448663287f069ef9dfea001e90f
LinuxLinux	Affected ≥ 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6, < 80fc6ca2cbde018d52e13f305edcd643911bd94b	Fixed in 80fc6ca2cbde018d52e13f305edcd643911bd94b

Description

In the Linux kernel, the following vulnerability has been resolved: md/raid5: fix soft lockup in retry_aligned_read() When retry_aligned_read() encounters an overlapped stripe, it releases the stripe via raid5_release_stripe() which puts it on the lockless released_stripes llist. In the next raid5d loop iteration, release_stripe_list() drains the stripe onto handle_list (since STRIPE_HANDLE is set by the original IO), but retry_aligned_read() runs before handle_active_stripes() and removes the stripe from handle_list via find_get_stripe() -> list_del_init(). This prevents handle_stripe() from ever processing the stripe to resolve the overlap, causing an infinite loop and soft lockup. Fix this by using __release_stripe() with temp_inactive_list instead of raid5_release_stripe() in the failure path, so the stripe does not go through the released_stripes llist. This allows raid5d to break out of its loop, and the overlap will be resolved when the stripe is eventually processed by handle_stripe().

References

Community reviews

Loading reviews…