[CVE-2026-72030][MODERATE 7.0] ata: libata-core: Reject an invalid concurrent positioning ranges count [ Upstream

[CVE-2026-72030][MODERATE 7.0] ata: libata-core: Reject an invalid concurrent positioning ranges count [ Upstream

[AL-KERNEL]

CVE: CVE-2026-72030
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: ata: libata-core: Reject an invalid concurrent positioning ranges count [ Upstream
Commit: 4cb4b4dd8853c4ab3057efe238b2c34277772176
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4cb4b4dd8853c4ab3057efe238b2c34277772176
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72030
Analysis date: Sat, 15 Aug 2026 05:12:40 -0400
ActionableScore: 6
ActionableScore lower bound: 4
Actionable bucket: Strong Important candidate / Actionable Moderate at minimum
Manual review required: YES

Summary:
A malicious or compromised ATA device can report an invalid Concurrent Positioning Ranges count that causes libata to read beyond the returned log and later overflow the fixed SCSI VPD B9h response buffer, making this a firmware-mediated kernel memory corruption and DoS issue requiring manual review.

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

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

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-72030	MODERATE	CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H';*CWE-787;CWE-125;*CWE-20;Other CVSS 'AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H';BEST CVSS score: '6.8';DESCR 'An invalid Concurrent Positioning Ranges count reported by an ATA device can make libata walk beyond the returned CPR log and can also make the VPD page B9h emitter write too many descriptors into the fixed ata_scsi_rbuf buffer. This is a memory corruption candidate because the same untrusted device supplied count controls both an out of bounds read from the log buffer and an out of bounds write into a fixed kernel response buffer. For the CVSS the PR:N is used because the triggering input is supplied by the attached ATA device or device firmware and does not require a local user account on the victim. The issue is not network reachable in normal deployments and exploitation usually requires physical access to attach a malicious ATA device or a compromised storage device already present in the system. Impact is at least denial of service via kernel memory corruption and in the paranoid case may include confidentiality and integrity impact, so this should be reviewed manually.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Strong Important candidate / Actionable Moderate at minimum (with actual score 5)	YES	OOB SIMPLEFIX LOG HARDWARE LINUS  DECREASED_TO_MODERATEREG_BASED_ON_FALSEPOSCHECKOFKP	YES	NO	checked

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

ActionableScore=6
ActionableScoreLower=4

## 1. ActionableScore

* Conservative score: 4
* Paranoid score: 6
* Final recommended bucket: **Strong Important candidate / Actionable Moderate at minimum**::

## 2. Signal breakdown

Conservative score signals:

* Firmware-mediated external influence: +1. The malformed CPR count is supplied by the ATA device or its firmware.
* Constrained kernel buffer overwrite: +1. The VPD B9h emitter can write beyond fixed `ata_scsi_rbuf`, but the target is a fixed kernel buffer and target selection is not shown.
* Reliable kernel crash / strong DoS: +1. The commit explicitly describes OOB read past a slab buffer and response-buffer overflow.
* Privileged kernel/device-management memory corruption path: +1. The bug is in libata probing and SCSI VPD emission, a trusted storage/device-management path.
* Physical-only or rare hardware-only condition: -2. Realistic triggering requires a malicious ATA device, compromised firmware, or controlled emulated storage device.
* Availability impact realistic: +1. Kernel memory corruption in this path can plausibly cause system-wide crash or storage-path failure.

Paranoid score differences:

* Memory corruption, strong corruption primitive: +2 instead of constrained +1. The patch context explicitly describes both OOB read and OOB write into kernel memory.
* Confidentiality impact plausible: +1. The OOB read path may expose adjacent kernel memory internally or influence later output paths, though no direct leak is demonstrated.
* Integrity impact plausible: +1. The fixed-buffer overflow is a kernel memory corruption candidate.
* Important filesystem/storage path: +1. ATA/libata and SCSI VPD handling are part of a core storage stack.

## 3. Reachability analysis

The trigger is not network reachable in normal deployments. The attacker generally needs control over an attached ATA device, malicious disk firmware, a compromised storage device, or an emulated ATA device presented to the host. Local namespaces or containers do not normally lower the trigger requirement, because the malformed input originates from hardware or firmware rather than a local syscall interface. The path can be reached during device probe/configuration and later VPD page B9h emission, but practical exploitation depends on uncommon attacker control over the storage device.

Call-site confidence: high. The commit explains both affected walks: CPR log parsing and VPD B9h emission into the fixed 2048-byte `ata_scsi_rbuf`.

## 4. Severity interpretation

This is above an ordinary Moderate because the patch fixes an explicitly described OOB read and OOB write in kernel storage code. Conservative handling should treat it as a firmware-mediated storage DoS and constrained corruption issue. Paranoid handling should keep it as Actionable Moderate because kernel memory corruption is present, even though realistic exploitation is limited by physical or firmware-level preconditions. It is not a normal remote or local-unprivileged LPE case based on the supplied patch.

## 5. One-sentence report phrase

A malicious or compromised ATA device can report an invalid Concurrent Positioning Ranges count that causes libata to read beyond the returned log and later overflow the fixed SCSI VPD B9h response buffer, making this a firmware-mediated kernel memory corruption and DoS issue requiring manual review.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: the patch explicitly describes OOB read and fixed-buffer overflow in a core storage/device path, so even though reachability is mostly physical or firmware-mediated, the memory corruption primitive should not be auto-closed.

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

Patch: ata: libata-core: Reject an invalid concurrent positioning ranges count [ Upstream
Commit: 4cb4b4dd8853c4ab3057efe238b2c34277772176
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4cb4b4dd8853c4ab3057efe238b2c34277772176

Changed files:
  drivers/ata/libata-core.c
  drivers/ata/libata-scsi.c
  drivers/ata/libata.h

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=4cb4b4dd8853c4ab3057efe238b2c34277772176

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

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

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

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: 4
  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: NO
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).