[CVE-2026-53021][MODERATE 7.0] scsi: target: core: Fix integer overflow in UNMAP bounds check [ Upstream

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-53021
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: scsi: target: core: Fix integer overflow in UNMAP bounds check [ Upstream
Commit: c08ab702c4699c6efb9d60bdb15b73e7a627ee7e
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c08ab702c4699c6efb9d60bdb15b73e7a627ee7e
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53021
Analysis date: Fri, 26 Jun 2026 14:11:50 -0400
ActionableScore: 6
ActionableScore lower bound: 5
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
An integer overflow in the SCSI target UNMAP bounds check may allow a remote or fabric-attached initiator with LUN access to bypass capacity validation and issue an invalid discard range, causing possible storage integrity loss or availability impact.

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

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

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: MODERATE 7.0
Manual review required: YES

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

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

CVE-2026-53021	MODERATE	CHECK	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H';CWE-190;*CWE-20;CWE-682;Other CVSS 'AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H';BEST CVSS score: '9.1';DESCR 'An integer overflow in the SCSI target UNMAP bounds check can occur when sbc_execute_unmap computes lba plus range without first checking for 64 bit wraparound. A remote or fabric attached initiator with access to the exported LUN may send a crafted UNMAP descriptor where the wrapped sum passes the capacity check, allowing an invalid discard range to reach the backend. For the CVSS the PR:N is used for the paranoid score because an exposed or weakly authenticated SCSI target can accept storage commands from a network initiator without local code execution on the target. The issue is network reachable for transports such as iSCSI when the target portal is exposed, while Fibre Channel or similar fabrics usually limit exposure to a storage network. Impact is primarily integrity and availability through unintended discard, backend errors, data loss, or storage service disruption. No direct kernel privilege escalation primitive is evident from the patch, but the storage data impact is strong enough to require manual review.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 6) 	MAYBE	OOB SIMPLEFIX HARDWARE  INCREASED_TO_HIGH_BASED_ON_GUESSCVSS8.5PLUS KPANIC DECREASED_TO_MODERATE70_BASED_ON_ACTIONABLESCORELOWERTHAN7	-	-	checked

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

ActionableScore=6
ActionableScoreLower=5

## 1. ActionableScore

* Conservative score: 5
* Paranoid score: 6
* Final recommended bucket: **Actionable Moderate at minimum**

## 2. Signal breakdown

Paranoid score signals:

* Remote reachable / network-triggerable: +2
  The affected path is in Linux SCSI target command handling. For iSCSI or other networked SCSI target transports, a remote or fabric-attached initiator can send UNMAP commands to an exported LUN.

* Reliable strong DoS / destructive storage impact: +1
  This is not a kernel memory corruption primitive, but a crafted UNMAP range may reach the backend after integer wraparound and can plausibly cause invalid discard behavior, backend errors, storage disruption, or data loss.

* Integrity impact plausible: +1
  UNMAP/DISCARD affects stored data semantics. If an invalid range is accepted, unintended discard or logical LUN corruption is a plausible integrity impact.

* Availability impact realistic: +1
  Storage disruption, backend errors, or data loss can affect availability beyond a transient warning.

* Important filesystem/storage path: +1
  The bug is in target_core_sbc.c, in the SCSI target block command path for exported storage.

Not counted:

* Generic memory corruption: +0
  The patch shows integer overflow in a storage bounds check, not UAF, OOB write, heap overwrite, or arbitrary kernel memory write.

* Privilege escalation plausible: +0
  No direct kernel privilege escalation primitive is supported by the patch.

* Admin penalty: 0
  The attacker does not need host admin privileges if they already have initiator access to the exported target. Access may still be controlled by target ACLs or fabric authentication.

## 3. Reachability analysis

A remote or fabric-attached SCSI initiator with access to an exported LUN can potentially trigger the bug by sending a crafted UNMAP descriptor with an LBA plus range value that wraps around 64 bits. For iSCSI this can be network reachable when the target portal is exposed to the attacker. For Fibre Channel, SRP, or similar fabrics, exposure is usually limited to a storage network.

The path is not default-enabled on all Linux systems because it requires Linux target mode and an exported block device. However, it is a normal production storage configuration and should not be treated as an obscure local-only debug path.

Namespaces and containers are not the main factor here. The relevant boundary is storage initiator access to the target LUN, including ACLs, authentication, and network or fabric segmentation.

## 4. Severity interpretation

This behaves more like an actionable Moderate storage integrity issue than an ordinary low-risk bounds-check cleanup. It is not an Important memory-corruption candidate because the patch does not show kernel memory corruption, reclaim control, arbitrary write, or privilege escalation.

The practical concern is that a malformed remote storage command can bypass the intended capacity check and allow an invalid discard range to proceed. That makes the issue important enough for manual triage, especially in iSCSI or exposed storage-target deployments.

## 5. One-sentence report phrase

An integer overflow in the SCSI target UNMAP bounds check may allow a remote or fabric-attached initiator with LUN access to bypass capacity validation and issue an invalid discard range, causing possible storage integrity loss or availability impact.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: the issue is not kernel memory corruption, but it is a remotely reachable storage command validation flaw in common target deployments and can plausibly affect LUN integrity and availability.

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

Patch: scsi: target: core: Fix integer overflow in UNMAP bounds check [ Upstream
Commit: c08ab702c4699c6efb9d60bdb15b73e7a627ee7e
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c08ab702c4699c6efb9d60bdb15b73e7a627ee7e

Changed files:
  drivers/target/target_core_sbc.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=c08ab702c4699c6efb9d60bdb15b73e7a627ee7e

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

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

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:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
  The Best / paranoid CVSS vector: AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
  The Best / paranoid CVSS score: 9.1

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: 5
  Paranoid ActionableScore: 6

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: MODERATE
KPANIC detected for this report: YES
Published priority for this report (same as in Subject): MODERATE 7.0

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