Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 22/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.09% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 09880592f5a9dc73377d6eb5ac123537b5f8df49, 1985cb3247e87ff6b8ca4bc5f9626f4f51024507, 4166d5234fe8b6c3c7f796a6c198605356c5b355; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 09880592f5a9dc73377d6eb5ac123537b5f8df49, 1985cb3247e87ff6b8ca4bc5f9626f4f51024507, 4166d5234fe8b6c3c7f796a6c198605356c5b355; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1 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/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().

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 27, 2026
Updated
Nov 6, 2026
EPSS
0.0% · 0th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.0%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

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.

Follow CVE-2026-46051

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

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 help

Affected 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.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel3.12 and later · before 5.10.258
  • linux linux kernel5.11 and later · before 5.15.209
  • linux linux kernel5.16 and later · before 6.1.175
  • linux linux kernel6.2 and later · before 6.6.140
  • linux linux kernel6.7 and later · before 6.12.86
  • linux linux kernel6.13 and later · before 6.18.27
  • linux linux kernel6.19 and later · before 7.0.4

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

    • 3.12affected
    • 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6 and later · before 66df9f30673db66ac35145820a8e24906069ae57affected · git
    • 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6 and later · before 4166d5234fe8b6c3c7f796a6c198605356c5b355affected · git
    • 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6 and later · before a9055300e07d9d6800264d3c2560e1d0144689caaffected · git
    • 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6 and later · before 09880592f5a9dc73377d6eb5ac123537b5f8df49affected · git
    • 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6 and later · before 80fc6ca2cbde018d52e13f305edcd643911bd94baffected · git
    • 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6 and later · before 1985cb3247e87ff6b8ca4bc5f9626f4f51024507affected · git
    • 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6 and later · before 883cc33b7af1c448663287f069ef9dfea001e90faffected · git
    • 773ca82fa1ee58dd1bf88b6a5ca385ec83a2cac6 and later · before 7f9f7c697474268d9ef9479df3ddfe7cdcfbbffcaffected · git
    • before 3.12not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.176-16.1.176-1
Debian:13linuxbefore 6.12.86-16.12.86-1
Debian:14linuxbefore 7.0.4-17.0.4-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-46049May 27, 2026 · ALSA: ctxfi: Add fallback to default RSR for S/PDIF
    22Monitor
  • ← EarlierCVE-2026-46050May 27, 2026 · md/raid10: fix deadlock with check operation and nowait requests
    22Monitor
  • Later →CVE-2026-46052May 27, 2026 · ceph: only d_add() negative dentries when they are unhashed
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux09880592f5a9dc73377d6eb5ac123537b5f8df49Vendor (CNA)
Linux Linux1985cb3247e87ff6b8ca4bc5f9626f4f51024507Vendor (CNA)
Linux Linux4166d5234fe8b6c3c7f796a6c198605356c5b355Vendor (CNA)
Linux Linux66df9f30673db66ac35145820a8e24906069ae57Vendor (CNA)
Linux Linux7f9f7c697474268d9ef9479df3ddfe7cdcfbbffcVendor (CNA)
Linux Linux80fc6ca2cbde018d52e13f305edcd643911bd94bVendor (CNA)
Linux Linux883cc33b7af1c448663287f069ef9dfea001e90fVendor (CNA)
Linux Linuxa9055300e07d9d6800264d3c2560e1d0144689caVendor (CNA)
azl3 kernel 6.6.139.1-1 on Azure Linux 3.06.6.141.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.176-1 · Debian:12Package 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 researchers

Finders, 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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records