CVE-2026-89827: drm/amdgpu: avoid force-completing uninitialized UVD rings

Published Sep 16, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu: avoid force-completing uninitialized UVD rings

uvdv70swinit() does not initialize the UVD decode ring for an SR-IOV VF. However, amdgpuuvdresume() unconditionally force-completes the decode ring when restoring its fence sequence.

Skip fence completion when the fence driver is not initialized.

Event History

Sep 16, 2026
CVE Published
via MITRE·10:30 AM
Data Sourced
via MITRE·10:30 AM
Description

Frequently Asked Questions

1

Which systems are exposed to this issue?

The affected path is specific to AMDGPU UVD version 7.0 running as an SR-IOV virtual function. The problem occurs because the UVD decode ring is not initialized for that VF configuration.

2

When is the vulnerable code path reached?

The issue is triggered when amdgpu_uvd_resume() restores the fence sequence and attempts to force-complete the UVD decode ring. In the affected SR-IOV VF case, that ring's fence driver has not been initialized.

3

What does the fix change?

The fix skips fence completion when the fence driver is not initialized, preventing force-completion of the uninitialized UVD decode ring.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203