CVE-2026-72030: Linux kernel · ata: libata-core: Reject an invalid concurrent positioning ranges count
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d43efd1b5d976203e6f1ef26f67e8b1a7bc2751b : update Linux kernel when convenient.
Data as of 6 Nov 2026, 17:04 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in d43efd1b5d976203e6f1ef26f67e8b1a7bc2751b, b1607f0ee5f5e53e0aa66f41794085b7cc98f5d1, 533a0b940f901c15e5cbbd4b5d66e871c209e8ce +3
Exploitation evidence
Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
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.
References
- git.kernel.org/stable/c/01d7d321e6046f87ba270aeeffdc5260209bd91e (opens in a new tab)
- git.kernel.org/stable/c/4cb4b4dd8853c4ab3057efe238b2c34277772176 (opens in a new tab)
- git.kernel.org/stable/c/b1607f0ee5f5e53e0aa66f41794085b7cc98f5d1 (opens in a new tab)
- git.kernel.org/stable/c/4c1e8ccd8655ee8cf1bcb1b7dfee72c9fa941fd4 (opens in a new tab)
- git.kernel.org/stable/c/d43efd1b5d976203e6f1ef26f67e8b1a7bc2751b (opens in a new tab)
- git.kernel.org/stable/c/533a0b940f901c15e5cbbd4b5d66e871c209e8ce (opens in a new tab)