CVE-2026-72030

ata: libata-core: Reject an invalid concurrent positioning ranges count

N/A
Published: August 15, 2026 at 05:51 AM UTC
Updated: August 23, 2026 at 01:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: ata: libata-core: Reject an invalid concurrent positioning ranges count ata_dev_config_cpr() takes the number of range descriptors from buf[0] of the concurrent positioning ranges log (up to 255), which the device reports independently of the log size in the GPL directory. The count is then walked at a fixed 32-byte stride in two places with no bound: the log read here, and the INQUIRY VPD page B9h emitter, which writes one descriptor per range into the fixed 2048-byte ata_scsi_rbuf. A device reporting a count larger than its own log overflows the read buffer (up to 7704 bytes past a 512-byte slab), and a count above 62 overflows the response buffer on the emit side. Bound the count once, on probe, against both the log the device returned and the number of descriptors the VPD B9h response buffer can hold (ATA_DEV_MAX_CPR, derived from the rbuf size). Reject an out-of-range count with a warning; this keeps the emitter in bounds with no separate change there.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.16 ≤ v < 6.1.1845.16 ≤ v < 6.12.1015.16 ≤ v < 6.18.425.16 ≤ v < 6.6.1485.16 ≤ v < 7.1.55.16 ≤ v < 7.25.16fe22e1c2f705676a705d821301fc52eecc2fe055
Vendor states this is fixed in 01d7d321e6046f87ba270aeeffdc5260209bd91e (fixed)
Vendor states this is fixed in 4c1e8ccd8655ee8cf1bcb1b7dfee72c9fa941fd4 (fixed)
Vendor states this is fixed in 4cb4b4dd8853c4ab3057efe238b2c34277772176 (fixed)
Vendor states this is fixed in 533a0b940f901c15e5cbbd4b5d66e871c209e8ce (fixed)
Vendor states this is fixed in b1607f0ee5f5e53e0aa66f41794085b7cc98f5d1 (fixed)
Vendor states this is fixed in d43efd1b5d976203e6f1ef26f67e8b1a7bc2751b (fixed)
Vendor states this is fixed in 5.16 (unaffected)
Vendor states this is fixed in 6.1.184 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card