cve.bz

CVE-2026-89827 linux linux

no score yetEPSS 0.2%Fix available

linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: avoid force-completing uninitialized UVD rings uvd_v7_0_sw_init() does not initialize the UVD decode ring for an SR-IOV VF. However, amdgpu_uvd_resume() unconditionally force-completes the decode ring when restoring its fence sequence. Skip fence completion when the fence driver is not initialized.
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 11th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 6.6.160
  • Linux Linux: fixed in 6.12.112
  • Linux Linux: fixed in 6.18.53
  • Linux Linux: fixed in 7.2.5
  • Linux Linux: fixed in 7.3
  • Debian, Ubuntu, openSUSE, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-89827 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-89827?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-89827?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-89827 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.5 and later

Fixed in

ProductRelease lineFixed in
Linux6.66.6.160
Linux6.126.12.112
Linux6.186.18.53
Linux7.27.2.5
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux-6.126.12.113-1~deb12u1DEBIAN-CVE-2026-89827
Debian13linux6.12.113-1DEBIAN-CVE-2026-89827
Debian14linux7.2.6-1DEBIAN-CVE-2026-89827
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-89827
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-89827
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-89827
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-89827 USN-9024-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-89827 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-89827 USN-9026-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-89827 USN-9024-1
Ubuntu22.04:LTSlinux-hwe-6.86.8.0-149.149~22.04.1UBUNTU-CVE-2026-89827 USN-9066-1
Ubuntu22.04:LTSlinux-ibm-6.86.8.0-1069.70~22.04.1UBUNTU-CVE-2026-89827 USN-9024-1
Ubuntu22.04:LTSlinux-lowlatency-hwe-6.86.8.0-149.149.1~22.04.1UBUNTU-CVE-2026-89827 USN-9024-1
Ubuntu22.04:LTSlinux-oracle-6.86.8.0-1067.71~22.04.1UBUNTU-CVE-2026-89827 USN-9025-1
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 31 moreno fix listedUBUNTU-CVE-2026-89827
43 more for Ubuntu in the JSON and on Ubuntu's page.
openSUSETumbleweedkernel-source7.2.7-1.1openSUSE-SU-2026:11880-1
Azure Linux3kernel6.6.161.1-1AZL-101303
Alpaquita25linux-lts6.12.112-r0BELL-CVE-2026-89827
Alpaquitastreamlinux-lts6.18.53-r0BELL-CVE-2026-89827

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

The AMDGPU UVD resume path can call amdgpu_fence_driver_force_completion for a decode ring whose fence driver was never initialized for an SR-IOV VF. Using this incomplete ring state can violate fence driver assumptions and may cause a warning or a host kernel crash during GPU resume or recovery. For the CVSS the PR:L value is used for the paranoid score because a restricted tenant or process with access to an assigned VF may be able to influence GPU workloads and recovery without having full host administrative privileges. Reliable triggering still depends on an SR-IOV VF configuration and on reaching the UVD resume or reset path, so AC:H is appropriate. The issue is not directly network reachable. The demonstrated impact is denial of service against the host, while the available code does not establish a UAF, information leak, or write primitive that would justify confidentiality or integrity impact.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Fix deferred
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-89827.

References

Check your stackJSON