Linux hwe edge: In the Linux kernel, the following vulnerability has been resolved: drm/radeon: Remove calls to drm_put_dev() Since the allocation of the drivers… (CVE-2025-68181)
In the Linux kernel, the following vulnerability has been resolved: drm/radeon: Remove calls to drm_put_dev() Since the allocation of the drivers main structure was changed to devm_drm_dev_alloc() drm_put_dev()'ing to trigger it to be free'd should be done by devres. However, drm_put_dev() is still in the probe error and device remove paths. When the driver fails to probe warnings like the following are shown because devres is trying to drm_put_dev() after the driver already did it. [ 5.642230] radeon 0000:01:05.0: probe with driver radeon failed with error -22 [ 5.649605] ------------[ cut here ]------------ [ 5.649607] refcount_t: underflow; use-after-free. [ 5.649620] WARNING: CPU: 0 PID: 357 at lib/refcount.c:28 refcount_warn_saturate+0xbe/0x110 (cherry picked from commit 3eb8c0b4c091da0a623ade0d3ee7aa4a93df1ea4)
AI Analysis
Technical Summary
The Linux kernel's Radeon DRM driver previously called drm_put_dev() redundantly after changing its main structure allocation to devm_drm_dev_alloc(), which handles freeing via devres. This caused refcount underflow and use-after-free errors during probe failures or device removal, as devres attempted to free an already freed resource. The vulnerability was fixed by removing these extra drm_put_dev() calls, preventing the use-after-free condition and associated kernel warnings.
Potential Impact
This vulnerability can cause use-after-free conditions leading to kernel memory corruption, which may be exploited to compromise system confidentiality, integrity, and availability. The CVSS vector indicates local attack vector with low complexity and privileges required, no user interaction, and high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
A fix has been applied in the Linux kernel by removing the redundant drm_put_dev() calls in the Radeon DRM driver. Users should update to the fixed kernel version containing commit 3eb8c0b4c091da0a623ade0d3ee7aa4a93df1ea4. Patch status is confirmed fixed in the kernel source. No additional mitigation is required beyond applying the official fix.
Linux hwe edge: In the Linux kernel, the following vulnerability has been resolved: drm/radeon: Remove calls to drm_put_dev() Since the allocation of the drivers… (CVE-2025-68181)
Description
In the Linux kernel, the following vulnerability has been resolved: drm/radeon: Remove calls to drm_put_dev() Since the allocation of the drivers main structure was changed to devm_drm_dev_alloc() drm_put_dev()'ing to trigger it to be free'd should be done by devres. However, drm_put_dev() is still in the probe error and device remove paths. When the driver fails to probe warnings like the following are shown because devres is trying to drm_put_dev() after the driver already did it. [ 5.642230] radeon 0000:01:05.0: probe with driver radeon failed with error -22 [ 5.649605] ------------[ cut here ]------------ [ 5.649607] refcount_t: underflow; use-after-free. [ 5.649620] WARNING: CPU: 0 PID: 357 at lib/refcount.c:28 refcount_warn_saturate+0xbe/0x110 (cherry picked from commit 3eb8c0b4c091da0a623ade0d3ee7aa4a93df1ea4)
CVSS v3.1
Score 7.8high
Affected software
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's Radeon DRM driver previously called drm_put_dev() redundantly after changing its main structure allocation to devm_drm_dev_alloc(), which handles freeing via devres. This caused refcount underflow and use-after-free errors during probe failures or device removal, as devres attempted to free an already freed resource. The vulnerability was fixed by removing these extra drm_put_dev() calls, preventing the use-after-free condition and associated kernel warnings.
Potential Impact
This vulnerability can cause use-after-free conditions leading to kernel memory corruption, which may be exploited to compromise system confidentiality, integrity, and availability. The CVSS vector indicates local attack vector with low complexity and privileges required, no user interaction, and high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
A fix has been applied in the Linux kernel by removing the redundant drm_put_dev() calls in the Radeon DRM driver. Users should update to the fixed kernel version containing commit 3eb8c0b4c091da0a623ade0d3ee7aa4a93df1ea4. Patch status is confirmed fixed in the kernel source. No additional mitigation is required beyond applying the official fix.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-5r23-9p29-3j75
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2025-68181"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a6b72d39c2644c7f8478904
Added to database: 07/30/2026, 15:50:43 UTC
Last enriched: 07/30/2026, 18:22:21 UTC
Last updated: 09/10/2026, 19:36:51 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.