CVE-2026-68238: drm/amdgpu: Release VFCT ACPI table reference

Published Aug 10, 2026
·
Updated

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

drm/amdgpu: Release VFCT ACPI table reference

amdgpuacpivfctbios() fetches the VFCT table with acpigettable() but never releases it. acpigettable() takes a reference on the table (incrementing its validationcount and mapping it on the 0->1 transition); without a paired acpiputtable() the mapping is leaked on every call, whether or not a matching VBIOS image is found.

Route all exit paths after the table is acquired through a common acpiputtable(). The VBIOS image is copied out with kmemdup() before the table is released, so it remains valid for the caller.

(cherry picked from commit ca5988682b4cba4cd125a0fa99b2de1239164ae4)

Affected Software

1 affected component
Linux Linux kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Linux kernel (amdgpu DRM) to a version that resolves this vulnerability.

    Patch drm/amdgpu: Release VFCT ACPI table reference

Event History

Aug 10, 2026
CVE Published
via MITRE·12:01 PM
Data Sourced
via MITRE·12:01 PM
Description
Data Sourced
via NVD·01:20 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-68238?

CVE-2026-68238 is rated with a risk score of 12.

2

How do I fix CVE-2026-68238?

To fix CVE-2026-68238, ensure you update to the patched version of the Linux kernel that addresses the VFCT ACPI table reference issue.

3

What systems are impacted by CVE-2026-68238?

CVE-2026-68238 affects systems running the affected versions of the Linux kernel that utilize the amdgpu driver.

4

What might happen if I don't resolve CVE-2026-68238?

If CVE-2026-68238 is not resolved, it could potentially lead to resource leaks, impacting system stability and performance.

5

When was CVE-2026-68238 published?

CVE-2026-68238 was published on August 10, 2026.

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