CVE-2026-80549: Linux kernel · s390/vfio_ccw: Move cp cleanup out of not operational
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 8.2 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:H/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: Move cp cleanup out of not operational The fsm_notoper() routine is called when the device has been lost, and is (by definition) no longer operational. Since this can happen asynchronously from the normal behavior of the driver, the cleanup may happen when holding other locks in the calling sequence (notably, the cio subchannel lock). Push the cleanup of the private->cp resources to a workqueue, where it can be done out from under that lock sequence and a future patch can safely manage the locking requirements.
References
- ubuntu.com/security/CVE-2026-80549 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-80549 (opens in a new tab)
- git.kernel.org/stable/c/f98a9890ca42f4223d2d4c50e0660af3e012fcb4 (opens in a new tab)
- git.kernel.org/stable/c/56100baa0eb7055b1026dfa73e696e8066ff71fd (opens in a new tab)
- git.kernel.org/stable/c/0c11f61a876ed6fcca53d442ed3f33ea8362a0f9 (opens in a new tab)
- git.kernel.org/stable/c/af1759d8e6e6da9ba94f30a2f92546f406899aa7 (opens in a new tab)
- git.kernel.org/stable/c/c9b85aa2cf73ea645e55e2c2670e0ddebfe1589b (opens in a new tab)
- git.kernel.org/stable/c/4e3301e2a651d742c05914f6074a25b8e41bce19 (opens in a new tab)
- ubuntu.com/security/notices/USN-8886-1 (opens in a new tab)