CVE-2026-80552: Linux kernel · s390/vfio_ccw: Ensure index for read/write regions are within range
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 8.8 High : upgrade to 6.8.0-1036.39 soon.
Data as of 28 Oct 2026, 01:00 UTC
- Patch
- Available – fixed in 6.8.0-1036.39
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 26 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade the Ubuntu linux-nvidia-tegra package to 6.8.0-1036.39.
Patches and advisories
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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.
References
- ubuntu.com/security/CVE-2026-80552 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-80552 (opens in a new tab)
- git.kernel.org/stable/c/d597fa1273802941c7801202135976fecc29672b (opens in a new tab)
- git.kernel.org/stable/c/3acbedf5c0b8e0971f0de423c05cc02bbf6ddb99 (opens in a new tab)
- git.kernel.org/stable/c/79ea5e0c4c8a9842ae85f45062d947b3297dfc07 (opens in a new tab)
- git.kernel.org/stable/c/9f5f9a78fedc45bc29d6a0a64e3a3472361afae5 (opens in a new tab)
- git.kernel.org/stable/c/649badf3a2fd8929e40198603a2cb21b74c21700 (opens in a new tab)
- git.kernel.org/stable/c/d3b1e38404b22df5a1f93019f2bb656feaad5ae3 (opens in a new tab)
- git.kernel.org/stable/c/988d9b5be3c2c4baf9457ce8e11b477e13eb9fcf (opens in a new tab)
- ubuntu.com/security/notices/USN-8886-1 (opens in a new tab)