ata: libata-core: Reject an invalid concurrent positioning ranges count
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Fixed version: Linux Linux 01d7d321e6046f87ba270aeeffdc5260209bd91e, 4c1e8ccd8655ee8cf1bcb1b7dfee72c9fa941fd4, 4cb4b4dd8853c4ab3057efe238b2c34277772176.
Low priority for now. Upgrade to Linux Linux 01d7d321e6046f87ba270aeeffdc5260209bd91e, 4c1e8ccd8655ee8cf1bcb1b7dfee72c9fa941fd4, 4cb4b4dd8853c4ab3057efe238b2c34277772176 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 15, 2026
- Updated
- Aug 23, 2026
- EPSS
- 0.2% · 9th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.16affected
- fe22e1c2f705676a705d821301fc52eecc2fe055 and later · before 01d7d321e6046f87ba270aeeffdc5260209bd91eaffected · git
- fe22e1c2f705676a705d821301fc52eecc2fe055 and later · before 4cb4b4dd8853c4ab3057efe238b2c34277772176affected · git
- fe22e1c2f705676a705d821301fc52eecc2fe055 and later · before b1607f0ee5f5e53e0aa66f41794085b7cc98f5d1affected · git
- fe22e1c2f705676a705d821301fc52eecc2fe055 and later · before 4c1e8ccd8655ee8cf1bcb1b7dfee72c9fa941fd4affected · git
- fe22e1c2f705676a705d821301fc52eecc2fe055 and later · before d43efd1b5d976203e6f1ef26f67e8b1a7bc2751baffected · git
- fe22e1c2f705676a705d821301fc52eecc2fe055 and later · before 533a0b940f901c15e5cbbd4b5d66e871c209e8ceaffected · git
- before 5.16not affected · semver
- 6.1.184 and later · up to and including 6.1.*not affected · semver
- 6.6.148 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 01d7d321e6046f87ba270aeeffdc5260209bd91e | Vendor (CNA) |
| Linux Linux | 4c1e8ccd8655ee8cf1bcb1b7dfee72c9fa941fd4 | Vendor (CNA) |
| Linux Linux | 4cb4b4dd8853c4ab3057efe238b2c34277772176 | Vendor (CNA) |
| Linux Linux | 533a0b940f901c15e5cbbd4b5d66e871c209e8ce | Vendor (CNA) |
| Linux Linux | b1607f0ee5f5e53e0aa66f41794085b7cc98f5d1 | Vendor (CNA) |
| Linux Linux | d43efd1b5d976203e6f1ef26f67e8b1a7bc2751b | Vendor (CNA) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/4c1e8ccd8655ee8cf1bcb1b7dfee72c9fa941fd4
- git.kernel.org/stable/c/4cb4b4dd8853c4ab3057efe238b2c34277772176
- git.kernel.org/stable/c/533a0b940f901c15e5cbbd4b5d66e871c209e8ce
- git.kernel.org/stable/c/b1607f0ee5f5e53e0aa66f41794085b7cc98f5d1
- git.kernel.org/stable/c/d43efd1b5d976203e6f1ef26f67e8b1a7bc2751b
Vendor advisories and official records. Exploit/PoC links are deliberately left out.