CVE-2026-80553: Linux kernel · s390/vfio_ccw: Cancel existing workqueues
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: Cancel existing workqueues The initialization of the io_work and crw_work workqueues begs the question of whether they should be un-initialized. Add the corresponding cleanup tags in _release_dev to ensure work isn't dispatched after the private struct is free'd.
References
- ubuntu.com/security/CVE-2026-80553 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-80553 (opens in a new tab)
- git.kernel.org/stable/c/b94b28c1f0fae53b2f2d6180ae6442c9a1558f67 (opens in a new tab)
- git.kernel.org/stable/c/b7ae0f7993867d009a4b554fc1d6d451c10580a0 (opens in a new tab)
- git.kernel.org/stable/c/79c60b2c61105368dcc8444eb45847e21734f7c4 (opens in a new tab)
- git.kernel.org/stable/c/e868ea8be0bc88c6982f48ecf3259d98afd884ae (opens in a new tab)
- git.kernel.org/stable/c/7492ca2d0c5d59add01e267be9f5a6eeb8076fd7 (opens in a new tab)
- git.kernel.org/stable/c/dc47a98abe6714577a25224534dbd356051097a3 (opens in a new tab)
- git.kernel.org/stable/c/87d569cb35a541b31a184faf982540694d4c9a89 (opens in a new tab)
- git.kernel.org/stable/c/77f5e888d2e607a0b3141fb95091ad6ef1cca9a2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8886-1 (opens in a new tab)