CVE-2025-68181
BaseFortify
Publication date: 2025-12-16
Last updated on: 2025-12-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability involves the Linux kernel's Radeon driver where calls to drm_put_dev() were not properly removed after changing the allocation method to devm_drm_dev_alloc(). As a result, drm_put_dev() was still called in error and device removal paths, causing warnings and a refcount underflow (use-after-free) when the driver fails to probe. This means the driver attempts to free resources twice, leading to potential memory corruption or instability.
How can this vulnerability impact me? :
The vulnerability can cause system instability or crashes due to use-after-free errors when the Radeon driver fails to initialize properly. This may lead to kernel warnings, potential memory corruption, and degraded system reliability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring system logs for specific warning messages related to the radeon driver probe failures. Look for kernel log entries similar to: "radeon 0000:01:05.0: probe with driver radeon failed with error -22" and warnings about refcount underflow such as "refcount_t: underflow; use-after-free." You can use the command `dmesg | grep radeon` or `journalctl -k | grep radeon` to find these messages in the kernel logs.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where the vulnerability is fixed, specifically one that includes the patch removing calls to drm_put_dev() in the radeon driver probe error and device remove paths. Until then, monitoring for the warning messages and avoiding triggering the radeon driver probe failures may reduce exposure.