Skip to main content

Over 150 LLM Providers · Over 5,300 Models The most extensible AI-powered pentesting platform. Open source. Star on GitHub

CVE-2025-68181

7.8 · HIGH
Published Dec 16, 2025 EPSS 0.14% (4th pctl)

Overview

CVE-2025-68181 is a high-severity vulnerability. It was published on December 16, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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)

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently Asked Questions

What is CVE-2025-68181?

CVE-2025-68181 is a high-severity vulnerability. It was published on December 16, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2025-68181?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2025-68181?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-68181?

CyberStrike's AI-powered security agents can automatically detect CVE-2025-68181 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.