[CVE-2026-45953][LOW] md/raid5: fix IO hang with degraded array with llbitmap [ Upstream

[CVE-2026-45953][LOW] md/raid5: fix IO hang with degraded array with llbitmap [ Upstream

[AL-KERNEL]

CVE: CVE-2026-45953
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: md/raid5: fix IO hang with degraded array with llbitmap [ Upstream
Commit: 870b9f15867b0e70f3459ef3974b043e8b229690
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=870b9f15867b0e70f3459ef3974b043e8b229690
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-45953
Analysis date: Wed, 27 May 2026 19:40:36 -0400
ActionableScore: 2
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
No one-sentence report phrase was found.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-45953 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-45953

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: LOW
Manual review required: NO

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-45953	LOW	CHECK	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';*CWE-835;**CWE-400;CWE-703;CWE-667;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'RAID5 with md llbitmap can deadloop when a degraded array handles writes whose bitmap state is still unwritten. handle_stripe_dirtying() can decide that reconstruct write is required, but need_this_block() did not apply the same blocks_synced check, so the stripe can be sent to fill handling while no block is selected and I/O makes no progress. For the CVSS the PR:L is used in the paranoid score because a local workload may write to an already configured degraded array, although creating and managing that state normally requires administrator control. The issue is not network reachable and does not provide a memory corruption primitive. Impact is availability only through I/O hang.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 2) 	MAYBE	DANGER DISK SIMPLEFIX IMPROVEONLY  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	-	-	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=2

1. ActionableScore
* Conservative score: 2
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate / Low-like**::

2. Signal breakdown
* Availability impact realistic: +1. The bug can deadloop stripe handling and hang I/O.
* Important filesystem/storage path: +1. The issue affects md RAID5 write handling with llbitmap in degraded arrays.
* Requires admin/root in typical deployments: -2. Creating and managing RAID5 degraded state and llbitmap setup normally requires administrator control.
* Paranoid local workload influence: +1. A local workload can write to an already configured degraded array and trigger the problematic stripe state.
* Hard/specific condition: -1. Requires RAID5, degraded state, llbitmap, unwritten bitmap state, and the affected write path.
* No memory corruption signal. This is a logic deadloop/I/O hang, not UAF, OOB, arbitrary write, info leak, or LPE.

3. Reachability analysis
The bug is reachable on an already configured md RAID5 array using llbitmap, especially when degraded and handling writes to not-yet-synced bitmap regions. Normal users may contribute write workload if they can write to the filesystem/block device, but configuring the array and degraded state is typically privileged. It is not network reachable.

4. Severity interpretation
This behaves like an ordinary Moderate or Low-like storage availability bug. The realistic impact is local I/O hang or degraded array write stall. There is no evidence of data disclosure, memory corruption, privilege escalation, or persistent metadata corruption beyond availability loss.

5. One-sentence report phrase
md RAID5 with llbitmap can deadloop degraded-array write handling when `need_this_block()` misses the `blocks_synced()` force-RCW condition, causing local I/O hang.

6. Manual review recommendation
NO MANUAL CHECK NEEDED. This is availability-only storage logic with specific configuration requirements and no memory corruption or privilege-escalation primitive.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: md/raid5: fix IO hang with degraded array with llbitmap [ Upstream
Commit: 870b9f15867b0e70f3459ef3974b043e8b229690
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=870b9f15867b0e70f3459ef3974b043e8b229690

Changed files:
  drivers/md/raid5.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=870b9f15867b0e70f3459ef3974b043e8b229690

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-45953 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-45953

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.7

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: unknown
  Paranoid ActionableScore: 2

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).