s390/vfio_ccw: Ensure index for read/write regions are within range
In the Linux kernel, the following vulnerability has been resolved: s390/vfio_ccw: Ensure index for read/write regions are within range The introduction of the capability chain rightly clamped the region indexes to the range of the capabilities itself, but neglected to do so for the existing read/write regions which should also be enforced.
- Published
- Aug 26, 2026
- Updated
- Aug 27, 2026
- EPSS
- 0.2% · 7th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
—
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.2affected
- db8e5d17ac03a65e2e0ee0ba50bf61a99741d871 and later · before 3acbedf5c0b8e0971f0de423c05cc02bbf6ddb99affected · git
- db8e5d17ac03a65e2e0ee0ba50bf61a99741d871 and later · before d3b1e38404b22df5a1f93019f2bb656feaad5ae3affected · git
- db8e5d17ac03a65e2e0ee0ba50bf61a99741d871 and later · before 79ea5e0c4c8a9842ae85f45062d947b3297dfc07affected · git
- db8e5d17ac03a65e2e0ee0ba50bf61a99741d871 and later · before d597fa1273802941c7801202135976fecc29672baffected · git
- db8e5d17ac03a65e2e0ee0ba50bf61a99741d871 and later · before 649badf3a2fd8929e40198603a2cb21b74c21700affected · git
- db8e5d17ac03a65e2e0ee0ba50bf61a99741d871 and later · before 988d9b5be3c2c4baf9457ce8e11b477e13eb9fcfaffected · git
- db8e5d17ac03a65e2e0ee0ba50bf61a99741d871 and later · before 9f5f9a78fedc45bc29d6a0a64e3a3472361afae5affected · git
- before 5.2not affected · semver
- 5.15.218 and later · up to and including 5.15.*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.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.10-1 | 7.1.10-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 | 3acbedf5c0b8e0971f0de423c05cc02bbf6ddb99 | Vendor (CNA) |
| Linux Linux | 649badf3a2fd8929e40198603a2cb21b74c21700 | Vendor (CNA) |
| Linux Linux | 79ea5e0c4c8a9842ae85f45062d947b3297dfc07 | Vendor (CNA) |
| Linux Linux | 988d9b5be3c2c4baf9457ce8e11b477e13eb9fcf | Vendor (CNA) |
| Linux Linux | 9f5f9a78fedc45bc29d6a0a64e3a3472361afae5 | Vendor (CNA) |
| Linux Linux | d3b1e38404b22df5a1f93019f2bb656feaad5ae3 | Vendor (CNA) |
| Linux Linux | d597fa1273802941c7801202135976fecc29672b | Vendor (CNA) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0919 · Aug 27, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
nvd-secondary
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
- git.kernel.org/stable/c/3acbedf5c0b8e0971f0de423c05cc02bbf6ddb99
- git.kernel.org/stable/c/649badf3a2fd8929e40198603a2cb21b74c21700
- git.kernel.org/stable/c/79ea5e0c4c8a9842ae85f45062d947b3297dfc07
- git.kernel.org/stable/c/988d9b5be3c2c4baf9457ce8e11b477e13eb9fcf
- git.kernel.org/stable/c/9f5f9a78fedc45bc29d6a0a64e3a3472361afae5
- git.kernel.org/stable/c/d3b1e38404b22df5a1f93019f2bb656feaad5ae3
- git.kernel.org/stable/c/d597fa1273802941c7801202135976fecc29672b
Vendor advisories and official records. Exploit/PoC links are deliberately left out.