Driver-unload failure via unreleased fence reference
Published Jan 31, 2026 · Updated Jan 31, 2026
Resource leak in Linux Kernel 6.16 through 6.18.6 leaves AMDGPU fence objects allocated during driver unload after queue teardown. The amdgpu_userq_fence_driver_free() path destroys the fence driver and its xarray without calling dma_fence_put() on userq->last_fence, so the retained reference keeps the final fence alive. The issue requires an AMDGPU user-mode queue with a last fence followed by driver unload, and it prevents the amdgpu_userq_fence slab cache from shutting down cleanly.
Summary
What happened
Resource leak in Linux Kernel 6.16 through 6.18.6 leaves AMDGPU fence objects allocated during driver unload after queue teardown. The amdgpu_userq_fence_driver_free() path destroys the fence driver and its xarray without calling dma_fence_put() on userq->last_fence, so the retained reference keeps the final fence alive. The issue requires an AMDGPU user-mode queue with a last fence followed by driver unload, and it prevents the amdgpu_userq_fence slab cache from shutting down cleanly.
The record
- CVE
- CVE-2026-23034
- Published
- Jan 31, 2026
- Updated
- Jan 31, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jan 31, 2026CVE publishedPublication date reported by the CVE source.
- Jan 31, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.16
- Affected versionversion=edc762a51c7181d6fe1e0837e2eb69afb406f98e <b2426a211dba6432e32a2e70e9183c6e134475c6
- Affected versionversion=edc762a51c7181d6fe1e0837e2eb69afb406f98e <e1a30e1ab33fc522785d04bbf7e1b13a5c5c9175
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo